Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1609909 > unrolled thread

Re: [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c

Started byJan Kara <jack@suse.cz>
First post2017-03-27 17:00 +0200
Last post2017-03-27 17:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [lkp-robot] [fsnotify]  0ee0efcf7c:  kernel_BUG_at_fs/notify/inotify/inotify_user.c Jan Kara <jack@suse.cz> - 2017-03-27 17:00 +0200

#1609909 — Re: [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c

FromJan Kara <jack@suse.cz>
Date2017-03-27 17:00 +0200
SubjectRe: [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c
Message-ID<tpEhI-17e-27@gated-at.bofh.it>
On Mon 27-03-17 12:36:17, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> commit: 0ee0efcf7c7968fb045454f621b5681e94b2c288 ("fsnotify: Move queueing of mark for destruction into fsnotify_put_mark()")
> https://git.kernel.org/cgit/linux/kernel/git/jack/linux-fs.git for_testing
> 
> in testcase: trinity
> with following parameters:
> 
> 	runtime: 300s
> 
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/

Yeah, the commit forgot to update assertion in inotify as ONESHOT watches
will now see one-less refcount (the protection still works right since they
are protected by SRCU in that case). Fixed.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web