{"push_id":2926877893,"size":4,"distinct_size":0,"ref":"refs/heads/next","head":"8319a69fa3b869e82059ab74cd45a3e370914300","before":"a1d3cd0a50f647f7b3b43139f083948ebcc5855b","commits":[{"sha":"d54f4fba889b205e9cd8239182ca5d27d0ac3bc2","author":{"name":"Amir Goldstein","email":"39b28f342388deb5b19584637eaeed658ed0d1e3@gmail.com"},"message":"fanotify: add API to attach/detach super block mark\n\nAdd another mark type flag FAN_MARK_FILESYSTEM for add/remove/flush\nof super block mark type.\n\nA super block watch gets all events on the filesystem, regardless of\nthe mount from which the mark was added, unless an ignore mask exists\non either the inode or the mount where the event was generated.\n\nOnly one of FAN_MARK_MOUNT and FAN_MARK_FILESYSTEM mark type flags\nmay be provided to fanotify_mark() or no mark type flag for inode mark.\n\nCc: <linux-api@vger.kernel.org>\nSigned-off-by: Amir Goldstein <amir73il@gmail.com>\nSigned-off-by: Jan Kara <jack@suse.cz>","distinct":false,"url":"https://api.github.com/repos/amir73il/linux/commits/d54f4fba889b205e9cd8239182ca5d27d0ac3bc2"},{"sha":"96a71f21ef1fcc32bea07c612a332a89a213f054","author":{"name":"Amir Goldstein","email":"39b28f342388deb5b19584637eaeed658ed0d1e3@gmail.com"},"message":"fanotify: store fanotify_init() flags in group's fanotify_data\n\nThis averts the need to re-generate flags in fanotify_show_fdinfo()\nand sets the scene for addition of more upcoming flags without growing\nnew members to the fanotify_data struct.\n\nSigned-off-by: Amir Goldstein <amir73il@gmail.com>\nSigned-off-by: Jan Kara <jack@suse.cz>","distinct":false,"url":"https://api.github.com/repos/amir73il/linux/commits/96a71f21ef1fcc32bea07c612a332a89a213f054"},{"sha":"7419dccc05969be33cedf05377adc3f5d2ce44b0","author":{"name":"Dave Chinner","email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com"},"message":"xfs: avoid lockdep false positives in xfs_trans_alloc\n\nWe've had a few reports of lockdep tripping over memory reclaim\ncontext vs filesystem freeze \"deadlocks\". They all have looked\nto be false positives on analysis, but it seems that they are\nbeing tripped because we take freeze references before we run\na GFP_KERNEL allocation for the struct xfs_trans.\n\nWe can avoid this false positive vector just by re-ordering the\noperations in xfs_trans_alloc(). That is. we need allocate the\nstructure before we take the freeze reference and enter the GFP_NOFS\nallocation context that follows the xfs_trans around. This prevents\nlockdep from seeing the GFP_KERNEL allocation inside the transaction\ncontext, and that prevents it from triggering the freeze level vs\nalloc context vs reclaim warnings.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>","distinct":false,"url":"https://api.github.com/repos/amir73il/linux/commits/7419dccc05969be33cedf05377adc3f5d2ce44b0"},{"sha":"8319a69fa3b869e82059ab74cd45a3e370914300","author":{"name":"Amir Goldstein","email":"39b28f342388deb5b19584637eaeed658ed0d1e3@gmail.com"},"message":"Merge remote-tracking branch 'jack/fsnotify' into next","distinct":false,"url":"https://api.github.com/repos/amir73il/linux/commits/8319a69fa3b869e82059ab74cd45a3e370914300"}]}
{"actor":{"display_login":"amir73il"}}