All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, gregkh@linuxfoundation.org, hch@lst.de,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	paulmck@kernel.org, phil@philpotter.co.uk,
	syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] kernel BUG at fs/ext4/inline.c:LINE!
Date: Mon, 29 Aug 2022 05:17:13 -0700	[thread overview]
Message-ID: <000000000000662b4a05e7603e42@google.com> (raw)
In-Reply-To: <0000000000004c915205b1a04ad9@google.com>

syzbot suspects this issue was fixed by commit:

commit 1045a06724f322ed61f1ffb994427c7bdbe64647
Author: Christoph Hellwig <hch@lst.de>
Date:   Wed Jun 29 15:01:02 2022 +0000

    remove CONFIG_ANDROID

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16ab0893080000
start commit:   a8ad9a2434dc Merge tag 'efi-urgent-for-v5.16-2' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=2ebd4b29568807bc
dashboard link: https://syzkaller.appspot.com/bug?extid=4faa160fa96bfba639f8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=114ae045b00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1785e92bb00000

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

#syz fix: remove CONFIG_ANDROID

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

  parent reply	other threads:[~2022-08-29 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 12:01 kernel BUG at fs/ext4/inline.c:LINE! syzbot
2021-12-13 19:01 ` [syzbot] " syzbot
2022-08-29 12:17 ` syzbot [this message]
2022-08-29 14:19   ` Greg KH
2022-08-30  7:46     ` Dmitry Vyukov

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=000000000000662b4a05e7603e42@google.com \
    --to=syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=phil@philpotter.co.uk \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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.