public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com>
Cc: NeilBrown <neilb@ownmail.net>,
	amir73il@gmail.com, brauner@kernel.org,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] WARNING in shmem_unlink (2)
Date: Fri, 28 Nov 2025 07:41:27 +0800	[thread overview]
Message-ID: <20251127234129.9487-1-hdanton@sina.com> (raw)
In-Reply-To: <176427972855.634289.8097806579329413784@noble.neil.brown.name>

On Fri, 28 Nov 2025 08:42:08 +1100 NeilBrown wrote:
> On Fri, 28 Nov 2025, syzbot wrote:
> > Hello,
> > 
> > syzbot found the following issue on:
> > 
> > HEAD commit:    30f09200cc4a Merge tag 'arm64-fixes' of git://git.kernel.o..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1047ee92580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=38a0c4cddc846161
> > dashboard link: https://syzkaller.appspot.com/bug?extid=bfc9a0ccf0de47d04e8c
> > compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1626ae12580000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1126ae12580000
> > 
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/a5630d1ab1eb/disk-30f09200.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/584408ed3fcf/vmlinux-30f09200.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/69749e493b1e/bzImage-30f09200.xz
> > 
> > The issue was bisected to:
> > 
> > commit d2c995581c7c5d0ff623b2700e76bf22499c66df
> > Author: NeilBrown <neil@brown.name>
> > Date:   Wed Jul 16 00:44:14 2025 +0000
> > 
> >     ovl: Call ovl_create_temp() without lock held.
> > 
> > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13db1e92580000
> > final oops:     https://syzkaller.appspot.com/x/report.txt?x=103b1e92580000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17db1e92580000
> > 
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com
> > Fixes: d2c995581c7c ("ovl: Call ovl_create_temp() without lock held.")
> 
> I think this was probably fixed by 
> Commit 1f480a181137 ("Add start_renaming_two_dentries()")
> 
> That patch replaced the call to ovl_lock_rename_workdir()
> with start_renaming_two_dentries()
> The new function checks that the two dentries are still hashed.
> 
> ovl_lock_rename_workdir() should have been changed to check
> that the dentries were still hashed before that patch that
> the bisect found which changed the locking in ovl_cleanup_and_whiteout.
> 
> Can you please confirm the bug no longer exists after that patch?
>
#syz test upstream master

  reply	other threads:[~2025-11-27 23:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 20:36 [syzbot] [overlayfs?] WARNING in shmem_unlink (2) syzbot
2025-11-27 21:42 ` NeilBrown
2025-11-27 23:41   ` Hillf Danton [this message]
2025-11-27 23:56     ` syzbot
2025-11-28  1:16     ` NeilBrown
2025-11-28  1:22 ` [PATCH] ovl: fail ovl_lock_rename_workdir() if either target is unhashed NeilBrown
2025-11-28  6:55   ` Hillf Danton
2025-11-28  7:28     ` [syzbot] [overlayfs?] WARNING in shmem_unlink (2) syzbot
2025-11-28  9:39   ` [PATCH] ovl: fail ovl_lock_rename_workdir() if either target is unhashed Christian Brauner
2025-11-28  9:54   ` Amir Goldstein

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=20251127234129.9487-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@ownmail.net \
    --cc=syzbot+bfc9a0ccf0de47d04e8c@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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