summaryrefslogtreecommitdiff
path: root/stun.h
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2015-11-10 19:25:46 +0100
committerTobias Klauser <tklauser@distanz.ch>2015-11-10 19:25:46 +0100
commit5c94119f5e03d5eb33b5b9717a4afa63522919ae (patch)
treef8b9db354401076bbb7bf58b4a4763eb043ae132 /stun.h
parent664dcf4217c4fc08cc43c050419fea8181d81ef1 (diff)
netsniff-ng: tcp: Don't print trailing space after last TCP flag name
Check whether there were flags printed before and if this is the case, add a space before printing the next flag. Nicely wrap this all in a macro. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'stun.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-20 14:22:40 +0000
00bb83eb10, but was ffff88043831c7b8 This is a regression caused by commit c19b3b05 ("xfs: mode di_mode to 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/devicetree')