From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+b74150fd2ef40e716ca2@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Christian Brauner <christian@brauner.io>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Forwarded: [PATCH] ipc/mqueue: fix dentry refcount imbalance in prepare_open()
Date: Sun, 30 Nov 2025 09:10:05 +0000 [thread overview]
Message-ID: <20251130091005.GU3538@ZenIV> (raw)
In-Reply-To: <20251130084612.GT3538@ZenIV>
On Sun, Nov 30, 2025 at 08:46:12AM +0000, Al Viro wrote:
> Mismerge in -next, actually.
... in vfs.all, fixed there since then.
commit 73612a36da1a09df19e205c6c6fd8a22ed441716
Merge: 6fda44ca8203 def1b1ed02b8
Author: Christian Brauner <brauner@kernel.org>
Date: Thu Nov 27 11:56:07 2025 +0100
Merge branch 'vfs-6.19.fd_prepare' into vfs.all
Signed-off-by: Christian Brauner <brauner@kernel.org>
# Conflicts:
# include/linux/cleanup.h
# ipc/mqueue.c
is where it happened and it's what -next has pulled.
Currently it's replaced with
commit d6ea5537c1a66a54d34f50d51ad201b1a2319ccf (vfs-common/vfs.all)
Merge: 80019251fa80 65c2c221846e
Author: Christian Brauner <brauner@kernel.org>
Date: Fri Nov 28 17:32:43 2025 +0100
Merge tag 'vfs-6.19-rc1.fd_prepare' of gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs into vfs.all
vfs-6.19-rc1.fd_prepare
Signed-off-by: Christian Brauner <brauner@kernel.org>
# -----BEGIN PGP SIGNATURE-----
#
# iHUEABYKAB0WIQRAhzRXHqcMeLMyaSiRxhvAZXjcogUCaSmOZwAKCRCRxhvAZXjc
# ouPcAQCFC+L9+ATyKDUpJj/7CS9PbHR9eSnBnwRfgafWY1wl5gD/c/0S7g6f7WTL
# nZwIMoQCAcUJDQpPlAcfNbUXKkwgWAA=
# =K19o
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 28 Nov 2025 12:58:31 CET
# gpg: using EDDSA key 408734571EA70C78B332692891C61BC06578DCA2
# gpg: Good signature from "Christian Brauner <christian@brauner.io>" [ultimate]
# gpg: aka "Christian Brauner <christian.brauner@getenv.org>" [ultimate]
# gpg: aka "Christian Brauner <brauner@kernel.org>" [ultimate]
# Conflicts:
# include/linux/cleanup.h
# ipc/mqueue.c
in there, and -next simply hasn't picked it yet.
next prev parent reply other threads:[~2025-11-30 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 13:05 [syzbot] [overlayfs?] WARNING in fast_dput syzbot
2025-11-29 21:58 ` Hillf Danton
2025-11-29 22:18 ` syzbot
2025-11-30 7:11 ` Forwarded: [PATCH] ipc/mqueue: fix dentry refcount imbalance in prepare_open() syzbot
2025-11-30 7:30 ` Al Viro
2025-11-30 8:46 ` Al Viro
2025-11-30 9:10 ` Al Viro [this message]
2025-11-30 10:52 ` [syzbot] [overlayfs?] WARNING in fast_dput Hillf Danton
2025-11-30 11:41 ` syzbot
2025-12-01 8:58 ` Amir Goldstein
2025-12-01 9:06 ` Al Viro
2025-12-01 9:07 ` Aleksandr Nogikh
2025-12-01 11:05 ` Amir Goldstein
2025-12-01 11:07 ` Aleksandr Nogikh
2025-12-01 12:11 ` Amir Goldstein
2025-12-01 10:18 ` 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=20251130091005.GU3538@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+b74150fd2ef40e716ca2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.