linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+a7b60a176ec13cafb793@syzkaller.appspotmail.com>
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	alex.gaynor@gmail.com, arve@android.com, brauner@kernel.org,
	cmllamas@google.com, gregkh@linuxfoundation.org,
	hridya@google.com, joel@joelfernandes.org, keescook@chromium.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	maco@android.com, minchan@kernel.org, ojeda@kernel.org,
	omosnace@redhat.com, surenb@google.com,
	syzkaller-bugs@googlegroups.com, tkjos@android.com,
	wedsonaf@google.com
Subject: Re: [syzbot] WARNING in find_vma
Date: Wed, 10 Aug 2022 14:48:41 +0100	[thread overview]
Message-ID: <YvO3OeojQ2aHVu67@casper.infradead.org> (raw)
In-Reply-To: <0000000000003ee71e05e5e33e10@google.com>

On Wed, Aug 10, 2022 at 06:44:08AM -0700, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit fd0016c6bd4f6287c5c5f98b6350033ebb3c9753
> Author: Miguel Ojeda <ojeda@kernel.org>
> Date:   Sun Dec 5 18:00:43 2021 +0000
> 
>     scripts: decode_stacktrace: demangle Rust symbols

This bisection has gone astray; those implicated in this commit can
ignore this report.  Liam has already posted a fix for the bug.


      parent reply	other threads:[~2022-08-10 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  7:34 syzbot
2022-08-08 19:33 ` syzbot
2022-08-08 22:32   ` Andrew Morton
2022-08-09 16:16     ` Liam Howlett
     [not found] ` <0000000000003ee71e05e5e33e10@google.com>
2022-08-10 13:48   ` Matthew Wilcox [this message]

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=YvO3OeojQ2aHVu67@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.gaynor@gmail.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hridya@google.com \
    --cc=joel@joelfernandes.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maco@android.com \
    --cc=minchan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=omosnace@redhat.com \
    --cc=surenb@google.com \
    --cc=syzbot+a7b60a176ec13cafb793@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tkjos@android.com \
    --cc=wedsonaf@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox