All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d79e205d463e603f47ff@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	david@redhat.com, gregkh@linuxfoundation.org,
	liam.howlett@oracle.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tj@kernel.org
Subject: Re: [syzbot] [kernfs?] WARNING: suspicious RCU usage in mas_start
Date: Thu, 27 Apr 2023 10:31:23 -0700	[thread overview]
Message-ID: <000000000000b4f18805fa54b9f7@google.com> (raw)
In-Reply-To: <0000000000003f3d9a05f56fcac5@google.com>

syzbot suspects this issue was fixed by commit:

commit 6db504ce55bdbc575723938fc480713c9183f6a2
Author: Liam R. Howlett <Liam.Howlett@oracle.com>
Date:   Wed Mar 8 22:03:10 2023 +0000

    mm/ksm: fix race with VMA iteration and mm_struct teardown

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1674715fc80000
start commit:   f3a2439f20d9 Merge tag 'rproc-v6.3' of git://git.kernel.or..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=dd442ddf29eaca0c
dashboard link: https://syzkaller.appspot.com/bug?extid=d79e205d463e603f47ff
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12cfaf1cc80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=149edbf0c80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: mm/ksm: fix race with VMA iteration and mm_struct teardown

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2023-04-27 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 10:42 [syzbot] [kernfs?] WARNING: suspicious RCU usage in mas_start syzbot
2023-02-27 15:29 ` syzbot
2023-04-27 17:31 ` syzbot [this message]
2023-04-27 17:47   ` Aleksandr Nogikh

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=000000000000b4f18805fa54b9f7@google.com \
    --to=syzbot+d79e205d463e603f47ff@syzkaller.appspotmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@kernel.org \
    /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.