From: syzbot <syzbot+cf0693aee9ea61dda749@syzkaller.appspotmail.com>
To: 42.hyeyoo@gmail.com, akpm@linux-foundation.org, axboe@kernel.dk,
brauner@kernel.org, cl@linux.com, cl@os.amperecomputing.com,
dvyukov@google.com, iamjoonsoo.kim@lge.com, jack@suse.cz,
keescook@chromium.org, linux-fsdevel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, penberg@kernel.org,
reiserfs-devel@vger.kernel.org, rientjes@google.com,
roman.gushchin@linux.dev, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz
Subject: Re: [syzbot] [reiserfs] kernel panic: stack is corrupted in ___slab_alloc
Date: Sun, 03 Mar 2024 01:21:03 -0800 [thread overview]
Message-ID: <000000000000c6b0fa0612be2070@google.com> (raw)
In-Reply-To: <0000000000002373f005ff843b58@google.com>
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=1629e3ca180000
start commit: e8f75c0270d9 Merge tag 'x86_sgx_for_v6.5' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a98ec7f738e43bd4
dashboard link: https://syzkaller.appspot.com/bug?extid=cf0693aee9ea61dda749
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10310670a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1220c777280000
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-03-03 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 17:17 [syzbot] [mm?] [reiserfs?] kernel panic: stack is corrupted in ___slab_alloc syzbot
2023-07-02 23:58 ` David Rientjes
2023-07-03 7:17 ` Dmitry Vyukov
2023-07-06 18:33 ` Lameter, Christopher
2023-07-10 7:43 ` Dmitry Vyukov
2023-07-10 7:48 ` Vlastimil Babka
2023-07-10 7:52 ` Dmitry Vyukov
2024-03-03 9:21 ` syzbot [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=000000000000c6b0fa0612be2070@google.com \
--to=syzbot+cf0693aee9ea61dda749@syzkaller.appspotmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cl@linux.com \
--cc=cl@os.amperecomputing.com \
--cc=dvyukov@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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.