)]}' { "log": [ { "commit": "fd657170c039a918c0b46f51db8005317d4c83fa", "tree": "ec6aaab2cdc8d31df93fd65f82ee503d429ff32e", "parents": [ "a4f9a9a635e4d54ac93df4b861ed8792e17bd4a2" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Tue May 29 11:02:24 2012 -0700" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Wed May 30 21:04:53 2012 -0400" }, "message": "fsnotify: remove unused parameter from send_to_group()\n\nWe don\u0027t use \"mnt\" anymore in send_to_group() after 1968f5eed5 (\"fanotify:\nuse both marks when possible\") was applied.\n\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "c63181e6b6df89176b3984c6977bb5ec03d0df23", "tree": "2e6056a7d85e8df9dbf95e6fa4291f76a714c7c8", "parents": [ "52ba1621de1479ce7e52b6d167860462e483313c" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Nov 25 02:35:16 2011 -0500" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Tue Jan 03 22:57:12 2012 -0500" }, "message": "vfs: move fsnotify junk to struct mount\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "873feea09ebc980cbd3631b767356ce1eee65ec1", "tree": "59a8fce9b138086abee7cf845f62ff70a390cf81", "parents": [ "ceb5bdc2d246f6d81cf61ed70f325308a11821d2" ], "author": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:50:06 2011 +1100" }, "committer": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:50:31 2011 +1100" }, "message": "fs: dcache per-inode inode alias locking\n\ndcache_inode_lock can be replaced with per-inode locking. Use existing\ninode-\u003ei_lock for this. This is slightly non-trivial because we sometimes\nneed to find the inode from the dentry, which requires d_inode to be\nstabilised (either with refcount or d_lock).\n\nSigned-off-by: Nick Piggin \u003cnpiggin@kernel.dk\u003e\n" }, { "commit": "b5c84bf6f6fa3a7dfdcb556023a62953574b60ee", "tree": "7a2c299a180713e21d5cb653cb933121adf53c31", "parents": [ "949854d02455080d20cd3e1db28a3a18daf7599d" ], "author": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:49:38 2011 +1100" }, "committer": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:50:23 2011 +1100" }, "message": "fs: dcache remove dcache_lock\n\ndcache_lock no longer protects anything. remove it.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@kernel.dk\u003e\n" }, { "commit": "b23fb0a60379a95e10c671f646b259ea2558421e", "tree": "7c3644b91241d32fda502a7be0b78e4c225f8091", "parents": [ "2fd6b7f50797f2e993eea59e0a0b8c6399c811dc" ], "author": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:49:35 2011 +1100" }, "committer": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:50:22 2011 +1100" }, "message": "fs: scale inode alias list\n\nAdd a new lock, dcache_inode_lock, to protect the inode\u0027s i_dentry list\nfrom concurrent modification. d_alias is also protected by d_lock.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@kernel.dk\u003e\n" }, { "commit": "2fd6b7f50797f2e993eea59e0a0b8c6399c811dc", "tree": "ce33b94b34844c09103836cf4cfa4364b742f217", "parents": [ "da5029563a0a026c64821b09e8e7b4fd81d3fe1b" ], "author": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:49:34 2011 +1100" }, "committer": { "name": "Nick Piggin", "email": "npiggin@kernel.dk", "time": "Fri Jan 07 17:50:21 2011 +1100" }, "message": "fs: dcache scale subdirs\n\nProtect d_subdirs and d_child with d_lock, except in filesystems that aren\u0027t\nusing dcache_lock for these anyway (eg. using i_mutex).\n\nNote: if we change the locking rule in future so that -\u003ed_child protection is\nprovided only with -\u003ed_parent-\u003ed_lock, it may allow us to reduce some locking.\nBut it would be an exception to an otherwise regular locking scheme, so we\u0027d\nhave to see some good results. Probably not worthwhile.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@kernel.dk\u003e\n" }, { "commit": "52420392c81c8712f555e6bcd116d8bd214ce43a", "tree": "372d23bba71ee687ff5adf5b83d3fd0706e19927", "parents": [ "ff8bcbd03da881bf1171910c6c07d44bd3c0a234" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Oct 28 17:21:56 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Oct 28 17:22:13 2010 -0400" }, "message": "fsnotify: call fsnotify_parent in perm events\n\nfsnotify perm events do not call fsnotify parent. That means you cannot\nregister a perm event on a directory and enforce permissions on all inodes in\nthat directory. This patch fixes that situation.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "ff8bcbd03da881bf1171910c6c07d44bd3c0a234", "tree": "ec7ad24bf2923bc19c48f1160a05328299193a8d", "parents": [ "2868201965419b9011f3f07fd80e765181343cb1" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Oct 28 17:21:56 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Oct 28 17:22:13 2010 -0400" }, "message": "fsnotify: correctly handle return codes from listeners\n\nWhen fsnotify groups return errors they are ignored. For permissions\nevents these should be passed back up the stack, but for most events these\nshould continue to be ignored.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "4d4eb36679adbdd75495e1bbfe7ac40e4ae41dea", "tree": "f5cef4647a54e8a65ab518db8edeeea6b7a8652d", "parents": [ "be9eee2e8b87e335531a3ae13abb8d26e834c438" ], "author": { "name": "Christoph Hellwig", "email": "hch@infradead.org", "time": "Sun Oct 10 05:36:30 2010 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Oct 25 21:26:14 2010 -0400" }, "message": "fsnotify: use dget_parent\n\nUse dget_parent instead of opencoding it. This simplifies the code, but\nmore importanly prepares for the more complicated locking for a parent\ndget in the dcache scale patch series.\n\nIt means we do grab a reference to the parent now if need to be watched,\nbut not with the specified mask. If this turns out to be a problem\nwe\u0027ll have to revisit it, but for now let\u0027s keep as much as possible\ndcache internals inside dcache.[ch].\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "92b4678efa8ce0de9b1e01a74e3d13c4002a4136", "tree": "97febbafb1798324802325c22c3693902a47323d", "parents": [ "f72adfd540bacc4f6ff57a7d708b1a6c8906bdb4" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Fri Aug 27 21:42:11 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Fri Aug 27 21:42:11 2010 -0400" }, "message": "fsnotify: drop two useless bools in the fnsotify main loop\n\nThe fsnotify main loop has 2 bools which indicated if we processed the\ninode or vfsmount mark in that particular pass through the loop. These\nbool can we replaced with the inode_group and vfsmount_group variables\nand actually make the code a little easier to understand.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "f72adfd540bacc4f6ff57a7d708b1a6c8906bdb4", "tree": "dffd43e47284095e98f2a2ab60f965fc68792008", "parents": [ "a2f13ad0ba5d94b9768c28469b45ca1e81a2b895" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Fri Aug 27 21:24:24 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Fri Aug 27 21:41:26 2010 -0400" }, "message": "fsnotify: fix list walk order\n\nMarks were stored on the inode and vfsmonut mark list in order from\nhighest memory address to lowest memory address. The code to walk those\nlists thought they were in order from lowest to highest with\nunpredictable results when trying to match up marks from each. It was\npossible that extra events would be sent to userspace when inode\nmarks ignoring events wouldn\u0027t get matched with the vfsmount marks.\n\nThis problem only affected fanotify when using both vfsmount and inode\nmarks simultaneously.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "84e1ab4d875922c034db7f4f814ac445a20a14bd", "tree": "79c5755b8293f69c81e9942eeb54a62a81c9dc4b", "parents": [ "88b2dbdbed551e4e21fdc8c56a15e198c52274e2" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Aug 18 12:25:50 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Sun Aug 22 20:09:41 2010 -0400" }, "message": "fsnotify: fix ignored mask handling between inode and vfsmount marks\n\nThe interesting 2 list lockstep walking didn\u0027t quite work out if the inode\nmarks only had ignores and the vfsmount list requested events. The code to\nshortcut list traversal would not run the inode list since it didn\u0027t have real\nevent requests. This code forces inode list traversal when a vfsmount mark\nmatches the event type. Maybe we could add an i_fsnotify_ignored_mask field\nto struct inode to get the shortcut back, but it doesn\u0027t seem worth it to grow\nstruct inode again.\n\nI bet with the recent changes to lock the way we do now it would actually not\nbe a major perf hit to just drop i_fsnotify_mark_mask altogether. But that is\nfor another day.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "5f3f259fa8f1d7969360acfad5307d03c2f53d63", "tree": "f1f781b5ebae2c03d27bd1a36bbd808eab8c7402", "parents": [ "faa9560ae76ef50a3cbfb1a6afc0343fd8172374" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Aug 18 12:25:49 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Sun Aug 22 20:09:41 2010 -0400" }, "message": "fsnotify: reset used_inode and used_vfsmount on each pass\n\nThe fsnotify main loop has 2 booleans which tell if a particular mark was\nsent to the listeners or if it should be processed in the next pass. The\nproblem is that the booleans were not reset on each traversal of the loop.\nSo marks could get skipped even when they were not sent to the notifiers.\n\nReported-by: Tvrtko Ursulin \u003ctvrtko.ursulin@sophos.com\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "faa9560ae76ef50a3cbfb1a6afc0343fd8172374", "tree": "b62dcdece22b214d0e0c75848b4d02b8e9923d0c", "parents": [ "3dc8d7f07e7496c0c6702e7e4b1acc179fa94019" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Aug 18 12:25:49 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Sun Aug 22 20:09:41 2010 -0400" }, "message": "fanotify: do not dereference inode_mark when it is unset\n\nThe fanotify code is supposed to get the group from the mark. It accidentally\nonly used the inode_mark. If the vfsmount_mark was set but not the inode_mark\nit would deref the NULL inode_mark. Get the group from the correct place.\n\nReported-by: Tvrtko Ursulin \u003ctvrtko.ursulin@sophos.com\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "2069601b3f0ea38170d4b509b89f3ca0a373bdc1", "tree": "647002d4c3814bd3d95d16ef7edef1757de8554f", "parents": [ "ad41a1e0cab07c5125456e8d38e5b1ab148d04aa" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Aug 12 14:23:04 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Aug 12 14:23:04 2010 -0700" }, "message": "Revert \"fsnotify: store struct file not struct path\"\n\nThis reverts commit 3bcf3860a4ff9bbc522820b4b765e65e4deceb3e (and the\naccompanying commit c1e5c954020e \"vfs/fsnotify: fsnotify_close can delay\nthe final work in fput\" that was a horribly ugly hack to make it work at\nall).\n\nThe \u0027struct file\u0027 approach not only causes that disgusting hack, it\nsomehow breaks pulseaudio, probably due to some other subtlety with\nf_count handling.\n\nFix up various conflicts due to later fsnotify work.\n\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "1968f5eed54ce47bde488fd9a450912e4a2d7138", "tree": "bcf13b98fda519c240e89cae3de95fc7d9ece715", "parents": [ "ce8f76fb7320297ccbe7c950fd9a2d727dd6a5a0" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:55 2010 -0400" }, "message": "fanotify: use both marks when possible\n\nfanotify currently, when given a vfsmount_mark will look up (if it exists)\nthe corresponding inode mark. This patch drops that lookup and uses the\nmark provided.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "ce8f76fb7320297ccbe7c950fd9a2d727dd6a5a0", "tree": "fb870e9564bfef438e46ba3c39be2999e246b179", "parents": [ "613a807fe7c793ceb7d6f059773527a5a6c84a96" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:54 2010 -0400" }, "message": "fsnotify: pass both the vfsmount mark and inode mark\n\nshould_send_event() and handle_event() will both need to look up the inode\nevent if they get a vfsmount event. Lets just pass both at the same time\nsince we have them both after walking the lists in lockstep.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "613a807fe7c793ceb7d6f059773527a5a6c84a96", "tree": "d217dbde37c8c0a145c36dea24e7afe5fe5e5ff0", "parents": [ "84a5b68e8da1490906c11129756490a556ae2c19" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:54 2010 -0400" }, "message": "fsnotify: walk the inode and vfsmount lists simultaneously\n\nWe currently walk the list of marks on an inode followed by the list of\nmarks on the vfsmount. These are in order (by the memory address of the\ngroup) so lets walk them both together. Eventually we can pass both the\ninode mark and the vfsmount mark to helpers simultaneously.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "84a5b68e8da1490906c11129756490a556ae2c19", "tree": "684be31165523f21dc844a6a56e84e23c04dba61", "parents": [ "02436668d98385f5b5d9ffb695a37dadf98ed8a8" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:54 2010 -0400" }, "message": "fsnotify: rework ignored mark flushing\n\ncurrently ignored_mark clearing is done in a seperate list traversal\nbefore the actual list traversal to send events. There is no need for\nthis. Do them at the same time.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "02436668d98385f5b5d9ffb695a37dadf98ed8a8", "tree": "e0e37328a9ba5c0af49903114fffd82f2141180d", "parents": [ "43709a288ed03aa0e2979ab63dd089b3889645c4" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:54 2010 -0400" }, "message": "fsnotify: remove global fsnotify groups lists\n\nThe global fsnotify groups lists were invented as a way to increase the\nperformance of fsnotify by shortcutting events which were not interesting.\nWith the changes to walk the object lists rather than global groups lists\nthese shortcuts are not useful.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "03930979afa63e079e9aefd4d3dd429240711027", "tree": "7df0097a8d51b9f71b4f10a0f49e773fb41d9ba5", "parents": [ "2612abb51b11ffd2d75c472b11178115f5808909" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:54 2010 -0400" }, "message": "fsnotify: remove the global masks\n\nBecause we walk the object-\u003efsnotify_marks list instead of the global\nfsnotify groups list we don\u0027t need the fsnotify_inode_mask and\nfsnotify_vfsmount_mask as these were simply shortcuts in fsnotify() for\nperformance. They are now extra checks, rip them out.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "2612abb51b11ffd2d75c472b11178115f5808909", "tree": "5657a07a347984cc1f34117d7ef88af73ea12b60", "parents": [ "0215054f377ce5ac4ffc27b26b13b3f10e6410e6" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:39 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:53 2010 -0400" }, "message": "fsnotify: cleanup should_send_event\n\nThe change to use srcu and walk the object list rather than the global\nfsnotify_group list means that should_send_event is no longer needed for a\nnumber of groups and can be simplified for others. Do that.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "3a9b16b407f10b2a771bcae13fb5791e527d6bcf", "tree": "0d88cac61bd6d3f5028eb0c9a45e7af9fbd24311", "parents": [ "8778abb9a88fc4a74d8776ffaadf7214cf33c61e" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:38 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:52 2010 -0400" }, "message": "fsnotify: send fsnotify_mark to groups in event handling functions\n\nWith the change of fsnotify to use srcu walking the marks list instead of\nwalking the global groups list we now know the mark in question. The code can\nsend the mark to the group\u0027s handling functions and the groups won\u0027t have to\nfind those marks themselves.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "75c1be487a690db43da2c1234fcacd84c982803c", "tree": "b38ce47f157d3b0eff7ac6eb4756a4b390ac35ae", "parents": [ "700307a29ad61090dcf1d45f8f4a135f5e9211ae" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:38 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:52 2010 -0400" }, "message": "fsnotify: srcu to protect read side of inode and vfsmount locks\n\nCurrently reading the inode-\u003ei_fsnotify_marks or\nvfsmount-\u003emnt_fsnotify_marks lists are protected by a spinlock on both the\nread and the write side. This patch protects the read side of those lists\nwith a new single srcu.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "3bcf3860a4ff9bbc522820b4b765e65e4deceb3e", "tree": "1e235af133559062c6fdee840ff9698f1dee26a6", "parents": [ "f70ab54cc6c3907b0727ba332b3976f80f3846d0" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:37 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:51 2010 -0400" }, "message": "fsnotify: store struct file not struct path\n\nAl explains that calling dentry_open() with a mnt/dentry pair is only\ngarunteed to be safe if they are already used in an open struct file. To\nmake sure this is the case don\u0027t store and use a struct path in fsnotify,\nalways use a struct file.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "5ba08e2eeb06355f66ed62ae97bb87d145973a9a", "tree": "4d0b26a125c8805234e0ebb58101bf1c5a75e61e", "parents": [ "80af2588676483ac4e998b5092e9d008dab3ab62" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:37 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:50 2010 -0400" }, "message": "fsnotify: add pr_debug throughout\n\nIt can be hard to debug fsnotify since there are so few printks. Use\npr_debug to allow for dynamic debugging.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "20dee624ca40db227aa70cb3f44d2d6cb4fdbab4", "tree": "527888dd4cda99501b7ac16a3783f57251807c13", "parents": [ "44b350fc23e36e95c8e042b7ded66217ea2b9d72" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:37 2010 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 10:18:50 2010 -0400" }, "message": "fsnotify: check to make sure all fsnotify bits are unique\n\nThis patch adds a check to make sure that all fsnotify bits are unique and we\ncannot accidentally use the same bit for 2 different fsnotify event types.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "98b5c10d320adfa250c1c18f3ccaec2f78e5e11d", "tree": "7ca8ca16bea8b514cd416fddb012108e8b74e83a", "parents": [ "8860f060e473dce1a0873d92105d536f72b05908" ], "author": { "name": "Jean-Christophe Dubois", "email": "jcd@tribudubois.net", "time": "Tue Mar 23 08:08:09 2010 +0100" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:59:02 2010 -0400" }, "message": "fanotify: do not always return 0 in fsnotify\n\nIt seems to me you are always returning 0 in fsnotify, when you should return\nthe error (EPERM) returned by fanotify.\n\nSigned-off-by: Jean-Christophe DUBOIS \u003cjcd@tribudubois.net\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "c4ec54b40d33f8016fea970a383cc584dd0e6019", "tree": "8e8865170cf340d1e79dc379f56417588715b2c8", "parents": [ "d14f1729483fad3a8817fbbcbd017678b7d1ad26" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:34 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:59:01 2010 -0400" }, "message": "fsnotify: new fsnotify hooks and events types for access decisions\n\nintroduce a new fsnotify hook, fsnotify_perm(), which is called from the\nsecurity code. This hook is used to allow fsnotify groups to make access\ncontrol decisions about events on the system. We also must change the\ngeneric fsnotify function to return an error code if we intend these hooks\nto be in any way useful.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "59b0df211bd9699d7e0d01fcf9345a149f75b033", "tree": "0f6e8bebfa090aa5c1d91d9efc5c2b04aeeed05c", "parents": [ "43ed7e16a8b47059d7f6ff67ba76f383a2421de3" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Mon Feb 08 12:53:52 2010 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:59:01 2010 -0400" }, "message": "fsnotify: use unsigned char * for dentry-\u003ed_name.name\n\nfsnotify was using char * when it passed around the d_name.name string\ninternally but it is actually an unsigned char *. This patch switches\nfsnotify to use unsigned and should silence some pointer signess warnings\nwhich have popped out of xfs. I do not add -Wpointer-sign to the fsnotify\ncode as there are still issues with kstrdup and strlen which would pop\nout needless warnings.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "c908370fc1ac27fd7e1fc0f34c693047b26564ce", "tree": "681cc398050764d04d34652c072790b8c1851d3e", "parents": [ "e898386146deb49a0b45ff1887d9da149c003209" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:33 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:59:00 2010 -0400" }, "message": "fsnotify: allow ignored_mask to survive modification\n\nSome inodes a group may want to never hear about a set of events even if\nthe inode is modified. We add a new mark flag which indicates that these\nmarks should not have their ignored_mask cleared on modification.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "e898386146deb49a0b45ff1887d9da149c003209", "tree": "6238ddb50919383139e7937c75a21524faacf03d", "parents": [ "b9e4e3bd0495fea9e8f8e712889c9cd8ffa43c94" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:33 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:59:00 2010 -0400" }, "message": "fsnotify: clear ignored mask on modify\n\nOn inode modification we clear the ignored mask for all of the marks on the\ninode. This allows userspace to ignore accesses to inodes until there is\nsomething different.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "ca9c726eea013394d1e846331b117effb21ead83", "tree": "de2319fb43b4fa16d07ecbcd75022cdaf9a757e1", "parents": [ "0d48b7f01f442bc88a69aa98f3b6b015f2817608" ], "author": { "name": "Andreas Gruenbacher", "email": "agruen@suse.de", "time": "Thu Dec 17 21:24:27 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:57 2010 -0400" }, "message": "fsnotify: Infrastructure for per-mount watches\n\nPer-mount watches allow groups to listen to fsnotify events on an entire\nmount. This patch simply adds and initializes the fields needed in the\nvfsmount struct to make this happen.\n\nSigned-off-by: Andreas Gruenbacher \u003cagruen@suse.de\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "2504c5d63b811b71bbaa8d5d5af163e698f4df1f", "tree": "4ff736af6b00fd5cbf0cd6a4d6bbcadb6dde9bd8", "parents": [ "ba643f04cdda170215c8820acd3e201936fc512d" ], "author": { "name": "Andreas Gruenbacher", "email": "agruen@suse.de", "time": "Thu Dec 17 21:24:27 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:57 2010 -0400" }, "message": "fsnotify/vfsmount: add fsnotify fields to struct vfsmount\n\nThis patch adds the list and mask fields needed to support vfsmount marks.\nThese are the same fields fsnotify needs on an inode. They are not used,\njust declared and we note where the cleanup hook should be (the function is\nnot yet defined)\n\nSigned-off-by: Andreas Gruenbacher \u003cagruen@suse.de\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "72acc854427948efed7a83da27f7dc3239ac9afc", "tree": "69a8f479a644701a52abe07d7bf2751cdf4cc159", "parents": [ "098cf2fc77ee190c92bf9d08d69a13305f2487ec" ], "author": { "name": "Andreas Gruenbacher", "email": "agruen@suse.de", "time": "Thu Dec 17 21:24:24 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:53 2010 -0400" }, "message": "fsnotify: kill FSNOTIFY_EVENT_FILE\n\nSome fsnotify operations send a struct file. This is more information than\nwe technically need. We instead send a struct path in all cases instead of\nsometimes a path and sometimes a file.\n\nSigned-off-by: Andreas Gruenbacher \u003cagruen@suse.de\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "3a9fb89f4cd04c23e16397befba92efb5d989b74", "tree": "f60b48c8cf488ad8952601ccbc6192b5f86ec900", "parents": [ "7131485a93679ff9a543b74df280cfd119eb03ca" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:23 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:52 2010 -0400" }, "message": "fsnotify: include vfsmount in should_send_event when appropriate\n\nTo ensure that a group will not duplicate events when it receives it based\non the vfsmount and the inode should_send_event test we should distinguish\nthose two cases. We pass a vfsmount to this function so groups can make\ntheir own determinations.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "7131485a93679ff9a543b74df280cfd119eb03ca", "tree": "d5d635cb37f77ef7ff8942e15de4c45f3fded940", "parents": [ "4ca763523e040dc61191d4866a82981a5d30a4e9" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:23 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:52 2010 -0400" }, "message": "fsnotify: mount point listeners list and global mask\n\ncurrently all of the notification systems implemented select which inodes\nthey care about and receive messages only about those inodes (or the\nchildren of those inodes.) This patch begins to flesh out fsnotify support\nfor the concept of listeners that want to hear notification for an inode\naccessed below a given monut point. This patch implements a second list\nof fsnotify groups to hold these types of groups and a second global mask\nto hold the events of interest for this type of group.\n\nThe reason we want a second group list and mask is because the inode based\nnotification should_send_event support which makes each group look for a mark\non the given inode. With one nfsmount listener that means that every group would\nhave to take the inode-\u003ei_lock, look for their mark, not find one, and return\nfor every operation. By seperating vfsmount from inode listeners only when\nthere is a inode listener will the inode groups have to look for their\nmark and take the inode lock. vfsmount listeners will have to grab the lock and\nlook for a mark but there should be fewer of them, and one vfsmount listener\nwon\u0027t cause the i_lock to be grabbed and released for every fsnotify group\non every io operation.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "19c2a0e1a2f60112c158342ba5f568f72b741c2c", "tree": "807520e66657e25420389c376cccaf5ca283f346", "parents": [ "0d2e2a1d00d7d23e5bd9bb0935cde7c3d5835c56" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:23 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:51 2010 -0400" }, "message": "fsnotify: rename fsnotify_groups to fsnotify_inode_groups\n\nSimple renaming patch. fsnotify is about to support mount point listeners\nso I am renaming fsnotify_groups and fsnotify_mask to indicate these are lists\nused only for groups which have watches on inodes.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "28c60e37f874dcbb93c4afc839ba5e4911c4f4bc", "tree": "6f0ba450d42e9e9d6cc5be2e42dc846f00c44447", "parents": [ "2a12a9d7814631e918dec93abad856e692d5286d" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:21 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:48 2010 -0400" }, "message": "fsnotify: send struct file when sending events to parents when possible\n\nfanotify needs a path in order to open an fd to the object which changed.\nCurrently notifications to inode\u0027s parents are done using only the inode.\nFor some parental notification we have the entire file, send that so\nfanotify can use it.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "8112e2d6a7356e8c3ff1f7f3c86f375ed0305705", "tree": "953926dd3596c0ac87d7407960d0987b765a8239", "parents": [ "7b0a04fbfb35650941af87728d4891515b4fc179" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:21 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:31 2010 -0400" }, "message": "fsnotify: include data in should_send calls\n\nfanotify is going to need to look at file-\u003eprivate_data to know if an event\nshould be sent or not. This passes the data (which might be a file,\ndentry, inode, or none) to the should_send function calls so fanotify can\nget that information when available\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "7b0a04fbfb35650941af87728d4891515b4fc179", "tree": "48d85a11a8d3c283db3eb9f91ac4fb97bb2beafe", "parents": [ "d7f0ce4e436b6109527c51b0efe0deff53d215f7" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Dec 17 21:24:21 2009 -0500" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 28 09:58:31 2010 -0400" }, "message": "fsnotify: provide the data type to should_send_event\n\nfanotify is only interested in event types which contain enough information\nto open the original file in the context of the fanotify listener. Since\nfanotify may not want to send events if that data isn\u0027t present we pass\nthe data type to the should_send_event function call so fanotify can express\nits lack of interest.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "5a0e3ad6af8660be21ca98a971cd00f331318c05", "tree": "5bfb7be11a03176a87296a43ac6647975c00a1d1", "parents": [ "ed391f4ebf8f701d3566423ce8f17e614cde9806" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Wed Mar 24 17:04:11 2010 +0900" }, "committer": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Tue Mar 30 22:02:32 2010 +0900" }, "message": "include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h\n\npercpu.h is included by sched.h and module.h and thus ends up being\nincluded when building most .c files. percpu.h includes slab.h which\nin turn includes gfp.h making everything defined by the two files\nuniversally available and complicating inclusion dependencies.\n\npercpu.h -\u003e slab.h dependency is about to be removed. Prepare for\nthis change by updating users of gfp and slab facilities include those\nheaders directly instead of assuming availability. As this conversion\nneeds to touch large number of source files, the following script is\nused as the basis of conversion.\n\n http://userweb.kernel.org/~tj/misc/slabh-sweep.py\n\nThe script does the followings.\n\n* Scan files for gfp and slab usages and update includes such that\n only the necessary includes are there. ie. if only gfp is used,\n gfp.h, if slab is used, slab.h.\n\n* When the script inserts a new include, it looks at the include\n blocks and try to put the new include such that its order conforms\n to its surrounding. It\u0027s put in the include block which contains\n core kernel includes, in the same order that the rest are ordered -\n alphabetical, Christmas tree, rev-Xmas-tree or at the end if there\n doesn\u0027t seem to be any matching order.\n\n* If the script can\u0027t find a place to put a new include (mostly\n because the file doesn\u0027t have fitting include block), it prints out\n an error message indicating which .h file needs to be added to the\n file.\n\nThe conversion was done in the following steps.\n\n1. The initial automatic conversion of all .c files updated slightly\n over 4000 files, deleting around 700 includes and adding ~480 gfp.h\n and ~3000 slab.h inclusions. The script emitted errors for ~400\n files.\n\n2. Each error was manually checked. Some didn\u0027t need the inclusion,\n some needed manual addition while adding it to implementation .h or\n embedding .c file was more appropriate for others. This step added\n inclusions to around 150 files.\n\n3. The script was run again and the output was compared to the edits\n from #2 to make sure no file was left behind.\n\n4. Several build tests were done and a couple of problems were fixed.\n e.g. lib/decompress_*.c used malloc/free() wrappers around slab\n APIs requiring slab.h to be added manually.\n\n5. The script was run on all .h files but without automatically\n editing them as sprinkling gfp.h and slab.h inclusions around .h\n files could easily lead to inclusion dependency hell. Most gfp.h\n inclusion directives were ignored as stuff from gfp.h was usually\n wildly available and often used in preprocessor macros. Each\n slab.h inclusion directive was examined and added manually as\n necessary.\n\n6. percpu.h was updated not to include slab.h.\n\n7. Build test were done on the following configurations and failures\n were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my\n distributed build env didn\u0027t work with gcov compiles) and a few\n more options had to be turned off depending on archs to make things\n build (like ipr on powerpc/64 which failed due to missing writeq).\n\n * x86 and x86_64 UP and SMP allmodconfig and a custom test config.\n * powerpc and powerpc64 SMP allmodconfig\n * sparc and sparc64 SMP allmodconfig\n * ia64 SMP allmodconfig\n * s390 SMP allmodconfig\n * alpha SMP allmodconfig\n * um on x86_64 SMP allmodconfig\n\n8. percpu.h modifications were reverted so that it could be applied as\n a separate patch and serve as bisection point.\n\nGiven the fact that I had only a couple of failures from tests on step\n6, I\u0027m fairly confident about the coverage of this conversion patch.\nIf there is a breakage, it\u0027s likely to be something in one of the arch\nheaders which should be easily discoverable easily on most builds of\nthe specific arch.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nGuess-its-ok-by: Christoph Lameter \u003ccl@linux-foundation.org\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Lee Schermerhorn \u003cLee.Schermerhorn@hp.com\u003e\n" }, { "commit": "f44aebcc566d1d6275f7191867b9633dc11de2ee", "tree": "a5faaf5ca8e1360f359ee22ad29582992596c3e6", "parents": [ "c05594b62125c528d93af3a78229793aae36df7f" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Wed Jul 15 15:49:52 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Tue Jul 21 15:26:27 2009 -0400" }, "message": "inotify: use GFP_NOFS under potential memory pressure\n\ninotify can have a watchs removed under filesystem reclaim.\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n[ INFO: inconsistent lock state ]\n2.6.31-rc2 #16\n---------------------------------\ninconsistent {IN-RECLAIM_FS-W} -\u003e {RECLAIM_FS-ON-W} usage.\nkhubd/217 [HC0[0]:SC0[0]:HE1:SE1] takes:\n (iprune_mutex){+.+.?.}, at: [\u003cc10ba899\u003e] invalidate_inodes+0x20/0xe3\n{IN-RECLAIM_FS-W} state was registered at:\n [\u003cc10536ab\u003e] __lock_acquire+0x2c9/0xac4\n [\u003cc1053f45\u003e] lock_acquire+0x9f/0xc2\n [\u003cc1308872\u003e] __mutex_lock_common+0x2d/0x323\n [\u003cc1308c00\u003e] mutex_lock_nested+0x2e/0x36\n [\u003cc10ba6ff\u003e] shrink_icache_memory+0x38/0x1b2\n [\u003cc108bfb6\u003e] shrink_slab+0xe2/0x13c\n [\u003cc108c3e1\u003e] kswapd+0x3d1/0x55d\n [\u003cc10449b5\u003e] kthread+0x66/0x6b\n [\u003cc1003fdf\u003e] kernel_thread_helper+0x7/0x10\n [\u003cffffffff\u003e] 0xffffffff\n\nTwo things are needed to fix this. First we need a method to tell\nfsnotify_create_event() to use GFP_NOFS and second we need to stop using\none global IN_IGNORED event and allocate them one at a time. This solves\ncurrent issues with multiple IN_IGNORED on a queue having tail drop\nproblems and simplifies the allocations since we don\u0027t have to worry about\ntwo tasks opperating on the IGNORED event concurrently.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "e42e27736de80045f925564ea27a1d32957219e7", "tree": "cae8a5bc81f02c7563625e30f5f0d05357dc3701", "parents": [ "ce61856bd2aadb064f595e5c0444376a2b117c41" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 11:09:47 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:54 2009 -0400" }, "message": "inotify/dnotify: should_send_event shouldn\u0027t match on FS_EVENT_ON_CHILD\n\ninotify and dnotify will both indicate that they want any event which came\nfrom a child inode. The fix is to mask off FS_EVENT_ON_CHILD when deciding\nif inotify or dnotify is interested in a given event.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\n" }, { "commit": "47882c6f51e8ef41fbbe2bbb746a1ea3228dd7ca", "tree": "d3dd3e8d0e4d3e3793f32107077839f787e35fcd", "parents": [ "62ffe5dfba056f7ba81d710fee9f28c58a42fdd6" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu May 21 17:01:47 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:54 2009 -0400" }, "message": "fsnotify: add correlations between events\n\nAs part of the standard inotify events it includes a correlation cookie\nbetween two dentry move operations. This patch includes the same behaviour\nin fsnotify events. It is needed so that inotify userspace can be\nimplemented on top of fsnotify.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\n" }, { "commit": "62ffe5dfba056f7ba81d710fee9f28c58a42fdd6", "tree": "ac0d4afc641bdc8ff76779545fde9c6ae539bdaf", "parents": [ "a2d8bc6cb4a3024661baf877242f123787d0c054" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu May 21 17:01:43 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:53 2009 -0400" }, "message": "fsnotify: include pathnames with entries when possible\n\nWhen inotify wants to send events to a directory about a child it includes\nthe name of the original file. This patch collects that filename and makes\nit available for notification.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\n" }, { "commit": "c28f7e56e9d95fb531dc3be8df2e7f52bee76d21", "tree": "efce13ed8c4f5b312ef0b77950489d52ef5a039a", "parents": [ "3be25f49b9d6a97eae9bcb96d3292072b7658bd8" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu May 21 17:01:29 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:53 2009 -0400" }, "message": "fsnotify: parent event notification\n\ninotify and dnotify both use a similar parent notification mechanism. We\nadd a generic parent notification mechanism to fsnotify for both of these\nto use. This new machanism also adds the dentry flag optimization which\nexists for inotify to dnotify.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\n" }, { "commit": "3be25f49b9d6a97eae9bcb96d3292072b7658bd8", "tree": "36f7d96481a47a6bde3c2f961346e940698111e0", "parents": [ "90586523eb4b349806887c62ee70685a49415124" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu May 21 17:01:26 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:53 2009 -0400" }, "message": "fsnotify: add marks to inodes so groups can interpret how to handle those inodes\n\nThis patch creates a way for fsnotify groups to attach marks to inodes.\nThese marks have little meaning to the generic fsnotify infrastructure\nand thus their meaning should be interpreted by the group that attached\nthem to the inode\u0027s list.\n\ndnotify and inotify will make use of these markings to indicate which\ninodes are of interest to their respective groups. But this implementation\nhas the useful property that in the future other listeners could actually\nuse the marks for the exact opposite reason, aka to indicate which inodes\nit had NO interest in.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\n" }, { "commit": "90586523eb4b349806887c62ee70685a49415124", "tree": "2ba6da637f897bbb2309b141b81801e4151d87b0", "parents": [ "c9059598ea8981d02356eead3188bf7fa4d717b8" ], "author": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu May 21 17:01:20 2009 -0400" }, "committer": { "name": "Eric Paris", "email": "eparis@redhat.com", "time": "Thu Jun 11 14:57:52 2009 -0400" }, "message": "fsnotify: unified filesystem notification backend\n\nfsnotify is a backend for filesystem notification. fsnotify does\nnot provide any userspace interface but does provide the basis\nneeded for other notification schemes such as dnotify. fsnotify\ncan be extended to be the backend for inotify or the upcoming\nfanotify. fsnotify provides a mechanism for \"groups\" to register for\nsome set of filesystem events and to then deliver those events to\nthose groups for processing.\n\nfsnotify has a number of benefits, the first being actually shrinking the size\nof an inode. Before fsnotify to support both dnotify and inotify an inode had\n\n unsigned long i_dnotify_mask; /* Directory notify events */\n struct dnotify_struct *i_dnotify; /* for directory notifications */\n struct list_head inotify_watches; /* watches on this inode */\n struct mutex inotify_mutex; /* protects the watches list\n\nBut with fsnotify this same functionallity (and more) is done with just\n\n __u32 i_fsnotify_mask; /* all events for this inode */\n struct hlist_head i_fsnotify_mark_entries; /* marks on this inode */\n\nThat\u0027s right, inotify, dnotify, and fanotify all in 64 bits. We used that\nmuch space just in inotify_watches alone, before this patch set.\n\nfsnotify object lifetime and locking is MUCH better than what we have today.\ninotify locking is incredibly complex. See 8f7b0ba1c8539 as an example of\nwhat\u0027s been busted since inception. inotify needs to know internal semantics\nof superblock destruction and unmounting to function. The inode pinning and\nvfs contortions are horrible.\n\nno fsnotify implementers do allocation under locks. This means things like\nf04b30de3 which (due to an overabundance of caution) changes GFP_KERNEL to\nGFP_NOFS can be reverted. There are no longer any allocation rules when using\nor implementing your own fsnotify listener.\n\nfsnotify paves the way for fanotify. In brief fanotify is a notification\nmechanism that delivers the lisener both an \u0027event\u0027 and an open file descriptor\nto the object in question. This means that fanotify is pathname agnostic.\nSome on lkml may not care for the original companies or users that pushed for\nTALPA, but fanotify was designed with flexibility and input for other users in\nmind. The readahead group expressed interest in fanotify as it could be used\nto profile disk access on boot without breaking the audit system. The desktop\nsearch groups have also expressed interest in fanotify as it solves a number\nof the race conditions and problems present with managing inotify when more\nthan a limited number of specific files are of interest. fanotify can provide\nfor a userspace access control system which makes it a clean interface for AV\nvendors to hook without trying to do binary patching on the syscall table,\nLSM, and everywhere else they do their things today. With this patch series\nfanotify can be implemented in less than 1200 lines of easy to review code.\nAlmost all of which is the socket based user interface.\n\nThis patch series builds fsnotify to the point that it can implement\ndnotify and inotify_user. Patches exist and will be sent soon after\nacceptance to finish the in kernel inotify conversion (audit) and implement\nfanotify.\n\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\n" } ] }