mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+65d101735df4bb19d2a3@syzkaller.appspotmail.com>
To: hdanton@sina.com, joannelkoong@gmail.com, josef@toxicpanda.com,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 miklos@szeredi.hu, mszeredi@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] kernel BUG in fuse_dev_do_write
Date: Sun, 20 Oct 2024 18:30:01 -0700	[thread overview]
Message-ID: <6715ae99.050a0220.10f4f4.003b.GAE@google.com> (raw)
In-Reply-To: <6714bb39.050a0220.10f4f4.002e.GAE@google.com>

syzbot has bisected this issue to:

commit 5d9e1455630d0f464f169bbd637dbb264cbd8ac8
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Mon Sep 30 13:45:18 2024 +0000

    fuse: convert fuse_notify_store to use folios

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=120dc25f980000
start commit:   15e7d45e786a Add linux-next specific files for 20241016
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=110dc25f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=160dc25f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c36416f1c54640c0
dashboard link: https://syzkaller.appspot.com/bug?extid=65d101735df4bb19d2a3
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1623e830580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16582f27980000

Reported-by: syzbot+65d101735df4bb19d2a3@syzkaller.appspotmail.com
Fixes: 5d9e1455630d ("fuse: convert fuse_notify_store to use folios")

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

  parent reply	other threads:[~2024-10-21  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20  8:11 syzbot
2024-10-20  9:39 ` Hillf Danton
2024-10-20 10:08   ` syzbot
2024-10-21  1:30 ` syzbot [this message]
2024-10-21  3:49   ` Hou Tao

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=6715ae99.050a0220.10f4f4.003b.GAE@google.com \
    --to=syzbot+65d101735df4bb19d2a3@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=joannelkoong@gmail.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®