linux-kernel - [RFC] VFS: mnotify (was: [PATCH 00/23] per device dirty throttling -v8)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <200708060625.20917.a1426z@gawab.com>
Date:	Mon, 6 Aug 2007 06:25:20 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-fsdevel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: [RFC] VFS: mnotify (was: [PATCH 00/23] per device dirty throttling -v8)

Jakob Oestergaard wrote:
> Why on earth would you cripple the kernel defaults for ext3 (which is a
> fine FS for boot/root filesystems), when the *fundamental* problem you
> really want to solve lie much deeper in the implementation of the
> filesystem?  Noatime doesn't solve the problem, it just makes it "less
> horrible".

inotify could easily solve the atime problem, but it's got the drawback of 
forcing the user to register each and every file/dir of interest, which 
isn't really reasonable on TB-filesystems.

It could be feasible to introduce mnotify, which would notify the user of 
meta changes, like atime, across the filesystem.  Something like mnotify 
could also be helpful in CoW situations, provided it supported an in-sync 
interface.

Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/