From: Al Viro <viro@zeniv.linux.org.uk>
To: NeilBrown <neil@brown.name>
Cc: Amir Goldstein <amir73il@gmail.com>,
Deepanshu Kartikey <kartikey406@gmail.com>,
brauner@kernel.org, jlayton@kernel.org,
linux-kernel@vger.kernel.org,
syzbot+b74150fd2ef40e716ca2@syzkaller.appspot.com
Subject: Re: [PATCH] ipc/mqueue: fix dentry refcount imbalance in prepare_open()
Date: Mon, 1 Dec 2025 09:00:01 +0000 [thread overview]
Message-ID: <20251201090001.GD3538@ZenIV> (raw)
In-Reply-To: <176457944867.16766.7275624308956648849@noble.neil.brown.name>
On Mon, Dec 01, 2025 at 07:57:28PM +1100, NeilBrown wrote:
> Al says it was a mismerge in -next, which has been resolved.
In vfs-common/vfs.all, actually, and it had been resolved there,
too late for the last -next of the week...
prev parent reply other threads:[~2025-12-01 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 9:27 [PATCH] ipc/mqueue: fix dentry refcount imbalance in prepare_open() Deepanshu Kartikey
2025-11-30 9:57 ` Amir Goldstein
2025-11-30 22:27 ` NeilBrown
2025-12-01 8:49 ` Amir Goldstein
2025-12-01 8:57 ` NeilBrown
2025-12-01 9:00 ` Al Viro [this message]
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=20251201090001.GD3538@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jlayton@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=syzbot+b74150fd2ef40e716ca2@syzkaller.appspot.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