public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Alan Huang <mmpgouride@gmail.com>
Cc: syzbot <syzbot+7836a68852a10ec3d790@syzkaller.appspotmail.com>,
	kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	miklos@szeredi.hu, amir73il@gmail.com,
	linux-unionfs@vger.kernel.org
Subject: Re: [syzbot] [bcachefs?] possible deadlock in bch2_symlink
Date: Mon, 4 Aug 2025 04:23:12 +0100	[thread overview]
Message-ID: <20250804032312.GX222315@ZenIV> (raw)
In-Reply-To: <2F4A26BA-821F-4916-A8F6-71EDBA89A701@gmail.com>

On Mon, Aug 04, 2025 at 11:02:54AM +0800, Alan Huang wrote:
> +cc overlayfs

Sigh...

1) ovl_copy_up_workdir() should lock wdir with I_MUTEX_PARENT, same
as filename_create().

2) what the hell is bch2_symlink() need to lock the new inode for?
page_symlink() doesn't need that; are there any bcachefs-specific reasons
to bother with that?

  reply	other threads:[~2025-08-04  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29  7:31 [syzbot] [bcachefs?] possible deadlock in bch2_symlink syzbot
2025-02-08  9:14 ` syzbot
2025-08-04  3:02   ` Alan Huang
2025-08-04  3:23     ` Al Viro [this message]
2025-08-04  3:27       ` Kent Overstreet
2025-08-18  9:19       ` Amir Goldstein
2025-08-18 10:41         ` syzbot
2025-08-04 23:12 ` Forwarded: 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=20250804032312.GX222315@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mmpgouride@gmail.com \
    --cc=syzbot+7836a68852a10ec3d790@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