Thread (67 messages) 67 messages, 9 authors, 2020-02-21

Re: [PATCH 00/19] VFS: Filesystem information and notifications [ver #16]

From: David Howells <dhowells@redhat.com>
Date: 2020-02-19 16:16:22
Also in: linux-fsdevel, lkml

Christian Brauner [off-list ref] wrote:
I mainly have an organizational question. :) This is a huge patchset
with lots and lots of (good) features. Wouldn't it make sense to make
the fsinfo() syscall a completely separate patchset from the
watch_mount() and watch_sb() syscalls? It seems that they don't need to
depend on each other at all. This would make reviewing this so much
nicer and likely would mean that fsinfo() could proceed a little faster.
I can split it up again, but it's not quite as independent as it seems.

There's a notification counter added to both the mount struct and the
super_block struct.  This is bumped by notifications and retrieved by
fsinfo().  You need this in the event that there's an overrun and you have to
rescan the whole tree.

So to actually make use of the mount/sb notification facilities, you need
fsinfo() as well.

David
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help