[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170327144852.GG6071@quack2.suse.cz>
Date: Mon, 27 Mar 2017 16:48:52 +0200
From: Jan Kara <jack@...e.cz>
To: kernel test robot <xiaolong.ye@...el.com>
Cc: Jan Kara <jack@...e.cz>, Amir Goldstein <amir73il@...il.com>,
LKML <linux-kernel@...r.kernel.org>, Jan Kara <jack@...e.com>,
lkp@...org
Subject: Re: [lkp-robot] [fsnotify] 0ee0efcf7c:
kernel_BUG_at_fs/notify/inotify/inotify_user.c
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@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists