From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+a3981d3c93cde53224be@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, bp@alien8.de, brauner@kernel.org,
dave.hansen@linux.intel.com, hpa@zytor.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, mingo@redhat.com,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [reiserfs?] possible deadlock in __run_timers
Date: Tue, 16 Jan 2024 10:25:08 +0100 [thread overview]
Message-ID: <CANp29Y5SSDgQYufDjvU01_NUfMmRsUSKKwu+WULS2JG_2ubkaA@mail.gmail.com> (raw)
In-Reply-To: <0000000000008e38b0060f0708bb@google.com>
#syz fix: fs: Block writes to mounted block devices
On Tue, Jan 16, 2024 at 3:39 AM syzbot
<syzbot+a3981d3c93cde53224be@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@suse.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152ab62be80000
> start commit: 88035e5694a8 Merge tag 'hid-for-linus-2023121201' of git:/..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=be2bd0a72b52d4da
> dashboard link: https://syzkaller.appspot.com/bug?extid=a3981d3c93cde53224be
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15befbfee80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b20006e80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: Block writes to mounted block devices
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
prev parent reply other threads:[~2024-01-16 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 19:50 [syzbot] [reiserfs?] possible deadlock in __run_timers syzbot
2024-01-16 2:39 ` syzbot
2024-01-16 9:25 ` Aleksandr Nogikh [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=CANp29Y5SSDgQYufDjvU01_NUfMmRsUSKKwu+WULS2JG_2ubkaA@mail.gmail.com \
--to=nogikh@google.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=mingo@redhat.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzbot+a3981d3c93cde53224be@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).