All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.com>,
	lkp@01.org
Subject: Re: [lkp-robot] [fsnotify]  0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c
Date: Mon, 27 Mar 2017 16:48:52 +0200	[thread overview]
Message-ID: <20170327144852.GG6071@quack2.suse.cz> (raw)
In-Reply-To: <20170327043617.GC17604@yexl-desktop>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c
Date: Mon, 27 Mar 2017 16:48:52 +0200	[thread overview]
Message-ID: <20170327144852.GG6071@quack2.suse.cz> (raw)
In-Reply-To: <20170327043617.GC17604@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

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

  reply	other threads:[~2017-03-27 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  4:36 [lkp-robot] [fsnotify] 0ee0efcf7c: kernel_BUG_at_fs/notify/inotify/inotify_user.c kernel test robot
2017-03-27  4:36 ` kernel test robot
2017-03-27 14:48 ` Jan Kara [this message]
2017-03-27 14:48   ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170327144852.GG6071@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=xiaolong.ye@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.