From: Christian Brauner <brauner@kernel.org>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "penguin-kernel@I-love.SAKURA.ne.jp"
<penguin-kernel@i-love.sakura.ne.jp>,
"jack@suse.cz" <jack@suse.cz>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"syzbot+f98189ed18c1f5f32e00@syzkaller.appspotmail.com"
<syzbot+f98189ed18c1f5f32e00@syzkaller.appspotmail.com>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"kapoorarnav43@gmail.com" <kapoorarnav43@gmail.com>
Subject: Re: [PATCH v3] hfsplus: pretend special inodes as regular files
Date: Wed, 14 Jan 2026 17:05:04 +0100 [thread overview]
Message-ID: <20260114-kleben-blitzen-4b50f7bad660@brauner> (raw)
In-Reply-To: <92748f200068dc1628f8e42c671e5a3a16c40734.camel@ibm.com>
On Tue, Jan 13, 2026 at 05:18:40PM +0000, Viacheslav Dubeyko wrote:
> On Tue, 2026-01-13 at 09:55 +0100, Christian Brauner wrote:
> > On Mon, 12 Jan 2026 18:39:23 +0900, Tetsuo Handa wrote:
> > > Since commit af153bb63a33 ("vfs: catch invalid modes in may_open()")
> > > requires any inode be one of S_IFDIR/S_IFLNK/S_IFREG/S_IFCHR/S_IFBLK/
> > > S_IFIFO/S_IFSOCK type, use S_IFREG for special inodes.
> > >
> > >
> >
> > Applied to the vfs-7.0.misc branch of the vfs/vfs.git tree.
> > Patches in the vfs-7.0.misc branch should appear in linux-next soon.
> >
> > Please report any outstanding bugs that were missed during review in a
> > new review to the original patch series allowing us to drop it.
> >
> > It's encouraged to provide Acked-bys and Reviewed-bys even though the
> > patch has now been applied. If possible patch trailers will be updated.
> >
> > Note that commit hashes shown below are subject to change due to rebase,
> > trailer updates or similar. If in doubt, please check the listed branch.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> > branch: vfs-7.0.misc
> >
> > [1/1] hfsplus: pretend special inodes as regular files
> > https://git.kernel.org/vfs/vfs/c/68186fa198f1
>
> I've already taken this patch into HFS/HFS+ tree. :) Should I remove it from the
> tree?
No, I'll drop it.
next prev parent reply other threads:[~2026-01-14 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 8:51 [syzbot] [hfs?] kernel BUG in may_open (3) syzbot
2026-01-12 9:27 ` Christian Brauner
2026-01-12 9:39 ` [PATCH v3] hfsplus: pretend special inodes as regular files Tetsuo Handa
2026-01-13 8:55 ` Christian Brauner
2026-01-13 17:18 ` Viacheslav Dubeyko
2026-01-14 16:05 ` Christian Brauner [this message]
2026-02-01 4:03 ` Tetsuo Handa
2026-02-02 17:30 ` Viacheslav Dubeyko
2026-02-02 21:50 ` Tetsuo Handa
2026-01-12 10:35 ` [syzbot] [hfs?] kernel BUG in may_open (3) Dmitry Vyukov
2026-01-12 9:31 ` Forwarded: Private message regarding: " syzbot
2026-02-07 9:48 ` 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=20260114-kleben-blitzen-4b50f7bad660@brauner \
--to=brauner@kernel.org \
--cc=Slava.Dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jack@suse.cz \
--cc=kapoorarnav43@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=slava@dubeyko.com \
--cc=syzbot+f98189ed18c1f5f32e00@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
all inboxes | Powered by JetHome®