diff options
| author | Brian Behlendorf <[email protected]> | 2019-01-18 11:11:47 -0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2019-01-18 11:11:47 -0800 |
| commit | ad635071355255a43469daa41fd411881407d861 (patch) | |
| tree | f443faa15c64916efe9dea69a8e361cc628f620e | |
| parent | b194fab0fb6caad18711abccaff3c69ad8b3f6d3 (diff) | |
Remove zfs_sync() panicking kernel check
This check provides no real additional protection and unnecessarily
introduces a dependency on the "oops_in_progress" kernel symbol.
Remove the check, it there are special circumstances on other
platforms which make this a requirement it can be reintroduced
for all relevant call paths in a more portable comprehensive manor.
Reviewed-by: Matt Ahrens <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #8297
| -rw-r--r-- | module/zfs/zfs_vfsops.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/module/zfs/zfs_vfsops.c b/module/zfs/zfs_vfsops.c index 74f444ebf..c9e314caa 100644 --- a/module/zfs/zfs_vfsops.c +++ b/module/zfs/zfs_vfsops.c @@ -259,13 +259,6 @@ zfs_sync(struct super_block *sb, int wait, cred_t *cr) zfsvfs_t *zfsvfs = sb->s_fs_info; /* - * Data integrity is job one. We don't want a compromised kernel - * writing to the storage pool, so we never sync during panic. - */ - if (unlikely(oops_in_progress)) - return (0); - - /* * Semantically, the only requirement is that the sync be initiated. * The DMU syncs out txgs frequently, so there's nothing to do. */ |