[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240219114906.nbjdxtnp6mdxvttv@quack3>
Date: Mon, 19 Feb 2024 12:49:06 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+0bc4c0668351ce1cab8f@...kaller.appspotmail.com>
Cc: almaz.alexandrovich@...agon-software.com, axboe@...nel.dk,
brauner@...nel.org, hdanton@...a.com, jack@...e.cz,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, nathan@...nel.org, ndesaulniers@...gle.com,
ntfs3@...ts.linux.dev, syzkaller-bugs@...glegroups.com,
trix@...hat.com
Subject: Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in
__lock_acquire (5)
On Sun 18-02-24 03:53:03, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.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@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists