All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7a278bf8bfa794494110@syzkaller.appspotmail.com>
To: amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	miklos@szeredi.hu, mszeredi@redhat.com,
	reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in delete_one_xattr (2)
Date: Sun, 24 Sep 2023 23:04:35 -0700	[thread overview]
Message-ID: <0000000000008a3693060628bb0b@google.com> (raw)
In-Reply-To: <000000000000964cb905f5e876ff@google.com>

syzbot has bisected this issue to:

commit 9df085f3c9a2d4658a9fe323d70c200aa00ede93
Author: Amir Goldstein <amir73il@gmail.com>
Date:   Mon Sep 3 06:12:09 2018 +0000

    ovl: relax requirement for non null uuid of lower fs

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1711e75a680000
start commit:   ac9a78681b92 Linux 6.4-rc1
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1491e75a680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1091e75a680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8bc832f563d8bf38
dashboard link: https://syzkaller.appspot.com/bug?extid=7a278bf8bfa794494110
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1295e4b8280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=140af20a280000

Reported-by: syzbot+7a278bf8bfa794494110@syzkaller.appspotmail.com
Fixes: 9df085f3c9a2 ("ovl: relax requirement for non null uuid of lower fs")

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

  parent reply	other threads:[~2023-09-25  6:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 10:40 [syzbot] [reiserfs?] possible deadlock in delete_one_xattr (2) syzbot
2023-05-08 16:48 ` syzbot
2023-09-25  6:04 ` syzbot [this message]
2023-09-25 10:14   ` Amir Goldstein
2023-09-25 10:14     ` Amir Goldstein

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=0000000000008a3693060628bb0b@google.com \
    --to=syzbot+7a278bf8bfa794494110@syzkaller.appspotmail.com \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --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 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.