Changes in Kconfig

818913fe - fs/notify: Remove "select SRCU"

Wed, 23 Nov 2022 01:52:19 +0000

fs/notify: Remove "select SRCU"Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it. Therefore, remove the "select SRCU"Kconfig statements.Signed-off-by: Paul E. McKenney Cc: Jan Kara Cc: Amir Goldstein Cc: Acked-by: Jan Kara Reviewed-by: John Ogness List of files: /linux-6.15/fs/notify/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/notify/Kconfig

83fe27ea - rcu: Make SRCU optional by using CONFIG_SRCU

Fri, 05 Dec 2014 16:24:45 +0000

rcu: Make SRCU optional by using CONFIG_SRCUSRCU is not necessary to be compiled by default in all cases. For tinificationefforts not compiling SRCU unless necessary is desirable.The current patch tries to make compiling SRCU optional by introducing a newKconfig option CONFIG_SRCU which is selected when any of the components makinguse of SRCU are selected.If we do not select CONFIG_SRCU, srcu.o will not be compiled at all. text data bss dec hex filename 2007 0 0 2007 7d7 kernel/rcu/srcu.oSize of arch/powerpc/boot/zImage changes from text data bss dec hex filename 831552 64180 23944 919676 e087c arch/powerpc/boot/zImage : before 829504 64180 23952 917636 e0084 arch/powerpc/boot/zImage : afterso the savings are about ~2000 bytes.Signed-off-by: Pranith Kumar CC: Paul E. McKenney CC: Josh Triplett CC: Lai Jiangshan Signed-off-by: Paul E. McKenney [ paulmck: resolve conflict due to removal of arch/ia64/kvm/Kconfig. ] List of files: /linux-6.15/fs/notify/Kconfig

9343919c - fanotify: allow fanotify to be built

Thu, 28 Oct 2010 21:21:56 +0000

fanotify: allow fanotify to be builtWe disabled the ability to build fanotify in commit 7c5347733dcc4ba0ba.This reverts that commit and allows people to build fanotify.Signed-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Kconfig

7c534773 - fanotify: disable fanotify syscalls

Mon, 11 Oct 2010 22:13:31 +0000

fanotify: disable fanotify syscallsThis patch disables the fanotify syscalls by just not building them andletting the cond_syscall() statements in kernel/sys_ni.c redirect themto sys_ni_syscall().It was pointed out by Tvrtko Ursulin that the fanotify interface did notinclude an explicit prioritization between groups. This is necessaryfor fanotify to be usable for hierarchical storage management software,as they must get first access to the file, before inotify-like notifierssee the file.This feature can be added in an ABI compatible way in the next release(by using a number of bits in the flags field to carry the info) but itwas suggested by Alan that maybe we should just hold off and do it inthe next cycle, likely with an (new) explicit argument to the syscall.I don't like this approach best as I know people are already starting touse the current interface, but Alan is all wise and noone on list backedme up with just using what we have. I feel this is needlessly rippingthe rug out from under people at the last minute, but if others think itneeds to be a new argument it might be the best way forward.Three choices:Go with what we got (and implement the new feature next cycle). Add anew field right now (and implement the new feature next cycle). Waittill next cycle to release the ABI (and implement the new feature nextcycle). This is number 3.Signed-off-by: Eric Paris Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/notify/Kconfig

ff0b16a9 - fanotify: fscking all notification system

Fri, 18 Dec 2009 02:24:25 +0000

fanotify: fscking all notification systemfanotify is a novel file notification system which bases notification ongiving userspace both an event type (open, close, read, write) and an openfile descriptor to the object in question. This should address a number ofraces and problems with other notification systems like inotify and dnotifyand should allow the future implementation of blocking or access controllednotification. These are useful for on access scanners or hierachical storagemanagement schemes.This patch just implements the basics of the fsnotify functions.Signed-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Kconfig

520dc2a5 - fsnotify: use def_bool in kconfig instead of letting the user choose

Mon, 13 Jul 2009 19:56:54 +0000

fsnotify: use def_bool in kconfig instead of letting the user choosefsnotify doens't give the user anything. If someone chooses inotify ordnotify it should build fsnotify, if they don't select one it shouldn't bebuilt. This patch changes fsnotify to be a def_bool=n and makes everythingelse select it. Also fixes the issue people complained about on lwn wheregdm hung because they didn't have inotify and they didn't get the inotifybuild option.....Signed-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Kconfig

90586523 - fsnotify: unified filesystem notification backend

Thu, 21 May 2009 21:01:20 +0000

fsnotify: unified filesystem notification backendfsnotify is a backend for filesystem notification. fsnotify doesnot provide any userspace interface but does provide the basisneeded for other notification schemes such as dnotify. fsnotifycan be extended to be the backend for inotify or the upcomingfanotify. fsnotify provides a mechanism for "groups" to register forsome set of filesystem events and to then deliver those events tothose groups for processing.fsnotify has a number of benefits, the first being actually shrinking the sizeof an inode. Before fsnotify to support both dnotify and inotify an inode had unsigned long i_dnotify_mask; /* Directory notify events */ struct dnotify_struct *i_dnotify; /* for directory notifications */ struct list_head inotify_watches; /* watches on this inode */ struct mutex inotify_mutex; /* protects the watches listBut with fsnotify this same functionallity (and more) is done with just __u32 i_fsnotify_mask; /* all events for this inode */ struct hlist_head i_fsnotify_mark_entries; /* marks on this inode */That's right, inotify, dnotify, and fanotify all in 64 bits. We used thatmuch space just in inotify_watches alone, before this patch set.fsnotify object lifetime and locking is MUCH better than what we have today.inotify locking is incredibly complex. See 8f7b0ba1c8539 as an example ofwhat's been busted since inception. inotify needs to know internal semanticsof superblock destruction and unmounting to function. The inode pinning andvfs contortions are horrible.no fsnotify implementers do allocation under locks. This means things likef04b30de3 which (due to an overabundance of caution) changes GFP_KERNEL toGFP_NOFS can be reverted. There are no longer any allocation rules when usingor implementing your own fsnotify listener.fsnotify paves the way for fanotify. In brief fanotify is a notificationmechanism that delivers the lisener both an 'event' and an open file descriptorto the object in question. This means that fanotify is pathname agnostic.Some on lkml may not care for the original companies or users that pushed forTALPA, but fanotify was designed with flexibility and input for other users inmind. The readahead group expressed interest in fanotify as it could be usedto profile disk access on boot without breaking the audit system. The desktopsearch groups have also expressed interest in fanotify as it solves a numberof the race conditions and problems present with managing inotify when morethan a limited number of specific files are of interest. fanotify can providefor a userspace access control system which makes it a clean interface for AVvendors to hook without trying to do binary patching on the syscall table,LSM, and everywhere else they do their things today. With this patch seriesfanotify can be implemented in less than 1200 lines of easy to review code.Almost all of which is the socket based user interface.This patch series builds fsnotify to the point that it can implementdnotify and inotify_user. Patches exist and will be sent soon afteracceptance to finish the in kernel inotify conversion (audit) and implementfanotify.Signed-off-by: Eric Paris Acked-by: Al Viro Cc: Christoph Hellwig List of files: /linux-6.15/fs/notify/Kconfig

272eb014 - filesystem notification: create fs/notify to contain all fs notification

Wed, 17 Dec 2008 18:59:41 +0000

filesystem notification: create fs/notify to contain all fs notificationCreating a generic filesystem notification interface, fsnotify, which will beused by inotify, dnotify, and eventually fanotify is really starting toclutter the fs directory. This patch simply moves inotify and dnotify intofs/notify/inotify and fs/notify/dnotify respectively to make both current fs/and future notification tidier.Signed-off-by: Eric Paris Signed-off-by: Al Viro List of files: /linux-6.15/fs/notify/Kconfig