diff options
| author | Josef Bacik <jbacik@fb.com> | 2015-10-22 15:05:09 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-03-03 15:07:11 -0800 |
| commit | 1106639221ef3eb80f3436785948c36e63d45b62 (patch) | |
| tree | 0c0cff0cf3fbb8d869dc5b48c705c80fbb7be6a4 /kernel/module_signing.c | |
| parent | 98d41a063d6584acc62ba1429ae074eac5d9d127 (diff) | |
Btrfs: igrab inode in writepage
commit be7bd730841e69fe8f70120098596f648cd1f3ff upstream.
We hit this panic on a few of our boxes this week where we have an
ordered_extent with an NULL inode. We do an igrab() of the inode in writepages,
but weren't doing it in writepage which can be called directly from the VM on
dirty pages. If the inode has been unlinked then we could have I_FREEING set
which means igrab() would return NULL and we get this panic. Fix this by trying
to igrab in btrfs_writepage, and if it returns NULL then just redirty the page
and return AOP_WRITEPAGE_ACTIVATE; so the VM knows it wasn't successful. Thanks,
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/module_signing.c')
0 files changed, 0 insertions, 0 deletions