* Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in __lock_acquire (5)
[not found] <0000000000004b7b3a05f0bc25f8@google.com>
@ 2024-02-18 11:53 ` syzbot
2024-02-19 11:49 ` Jan Kara
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2024-02-18 11:53 UTC (permalink / raw)
To: almaz.alexandrovich, axboe, brauner, hdanton, jack, linux-fsdevel,
linux-kernel, llvm, nathan, ndesaulniers, ntfs3, syzkaller-bugs,
trix
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=1301e1d0180000
start commit: ce9ecca0238b Linux 6.6-rc2
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e4ca82a1bedd37e4
dashboard link: https://syzkaller.appspot.com/bug?extid=0bc4c0668351ce1cab8f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11814954680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103bc138680000
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in __lock_acquire (5)
2024-02-18 11:53 ` [syzbot] [ntfs3?] kernel panic: stack is corrupted in __lock_acquire (5) syzbot
@ 2024-02-19 11:49 ` Jan Kara
0 siblings, 0 replies; 2+ messages in thread
From: Jan Kara @ 2024-02-19 11:49 UTC (permalink / raw)
To: syzbot
Cc: almaz.alexandrovich, axboe, brauner, hdanton, jack, linux-fsdevel,
linux-kernel, llvm, nathan, ndesaulniers, ntfs3, syzkaller-bugs,
trix
On Sun 18-02-24 03:53:03, syzbot 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=1301e1d0180000
> start commit: ce9ecca0238b Linux 6.6-rc2
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e4ca82a1bedd37e4
> dashboard link: https://syzkaller.appspot.com/bug?extid=0bc4c0668351ce1cab8f
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11814954680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103bc138680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
Again. Nothing really suspicious in the reproducer but there are no working
reproducers anymore... Since this is ntfs3:
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-02-19 11:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <0000000000004b7b3a05f0bc25f8@google.com>
2024-02-18 11:53 ` [syzbot] [ntfs3?] kernel panic: stack is corrupted in __lock_acquire (5) syzbot
2024-02-19 11:49 ` Jan Kara
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 NNTP newsgroup(s).