From: David Sterba <dsterba@suse.cz>
To: syzbot <syzbot+85e58cdf5b3136471d4b@syzkaller.appspotmail.com>
Cc: amir73il@gmail.com, brauner@kernel.org, clm@fb.com,
dsterba@suse.com, jack@suse.cz, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, mszeredi@redhat.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [btrfs?] [overlayfs?] possible deadlock in ovl_copy_up_flags
Date: Thu, 23 May 2024 18:43:12 +0200 [thread overview]
Message-ID: <20240523164312.GD17126@twin.jikos.cz> (raw)
In-Reply-To: <000000000000f6865106191c3e58@google.com>
On Thu, May 23, 2024 at 03:09:26AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: c75962170e49 Add linux-next specific files for 20240517
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1438a5cc980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=fba88766130220e8
> dashboard link: https://syzkaller.appspot.com/bug?extid=85e58cdf5b3136471d4b
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115f3e58980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f4c97c980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/21696f8048a3/disk-c7596217.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b8c71f928633/vmlinux-c7596217.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/350bfc6c0a6a/bzImage-c7596217.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/7f6a8434331c/mount_0.gz
>
> The issue was bisected to:
>
> commit 9a87907de3597a339cc129229d1a20bc7365ea5f
> Author: Miklos Szeredi <mszeredi@redhat.com>
> Date: Thu May 2 18:35:57 2024 +0000
>
> ovl: implement tmpfile
In the C reproducer it's btrfs + overlayfs, this more looks like a bug in
overlayfs handling the tmpfile and sb_*_write accross layers. Btrfs
functions are not on the stack.
#syz set subsystems: overlayfs
next prev parent reply other threads:[~2024-05-23 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 10:09 [syzbot] [btrfs?] [overlayfs?] possible deadlock in ovl_copy_up_flags syzbot
2024-05-23 16:43 ` David Sterba [this message]
2024-05-27 13:50 ` Miklos Szeredi
2024-05-27 21:36 ` [syzbot] [overlayfs] " syzbot
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=20240523164312.GD17126@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--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=syzbot+85e58cdf5b3136471d4b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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