summaryrefslogtreecommitdiff
path: root/tstamping.h
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2016-04-30 09:33:13 +0200
committerTobias Klauser <tklauser@distanz.ch>2016-04-30 09:35:00 +0200
commit6f3886dcf06337eeb2a1f8cf72305778f7a95381 (patch)
tree44a102f69e1c22a50afbaaa40c0888df6b94a053 /tstamping.h
parent8a02953bd666fb4b6437cfe272c321b0b6023848 (diff)
man: mausezahn: Fix man warnings
Fix warnings such as the following, reported by lintian [1]: usr/share/man/man8/mausezahn.8.gz 106: warning: macro `'own''' not defined [1] https://lintian.debian.org/maintainer/daniel.borkmann@alumni.ethz.ch.html#netsniff-ng Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'tstamping.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-15 09:41:23 +0000
o vfs inode"). The issue is that xfs_inactive() frees the unlinked inode, and the above commit meant that this freeing zeroed the mode in the struct inode. The problem is that after evict() has called ->evict_inode, it expects the i_mode to be intact so that it can call bd_forget() or cd_forget() to drop the reference to the block device inode attached to the XFS inode. In reality, the only thing we do in xfs_fs_evict_inode() that is not generic is call xfs_inactive(). We can move the xfs_inactive() call to xfs_fs_destroy_inode() without any problems at all, and this will leave the VFS inode intact until it is completely done with it. So, remove xfs_fs_evict_inode(), and do the work it used to do in ->destroy_inode instead. cc: <stable@vger.kernel.org> # 4.6 Reported-by: Joe Lawrence <joe.lawrence@stratus.com> Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Brian Foster <bfoster@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'Documentation/early-userspace')