From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
frank.li@vivo.com, jkoolstra@xs4all.nl,
mehdi.benhadjkhelifa@gmail.com, shardul.b@mpiricsoftware.com,
torvalds@linux-foundation.org
Subject: Re: [GIT PULL] hfs/hfsplus changes for 7.0-rc1
Date: Sat, 7 Feb 2026 18:44:52 +0900 [thread overview]
Message-ID: <202dc17c-99dc-4dbd-afae-bb148e7cb025@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <66af2e9a17dab9f1ef79ad5812ec91aa9c0be005.camel@physik.fu-berlin.de>
On 2026/02/07 17:55, John Paul Adrian Glaubitz wrote:
> Hi Tetsuo,
>
> On Sat, 2026-02-07 at 10:18 +0900, Tetsuo Handa wrote:
>> On 2026/02/07 9:26, Viacheslav Dubeyko wrote:
>>> Hello Linus,
>>>
>>> This pull request contains several fixes of syzbot reported
>>> issues and HFS+ fixes of xfstests failures.
>>
>> Where is the flow for testing these patches in linux-next tree?
>> Are HFS/HFS+ patches directly going to linux tree without testing
>> in linux-next tree?
>
> The HFS/HFS+ tree should be part of linux-next which is why it's got
> a branch named like this [1].
>
> Adrian
>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git/log/?h=for-next
>
Oops, the patch with old Reported-by: was applied. That's why I can't find
"hfsplus: pretend special inodes as regular files" as a fix commit for
https://syzkaller.appspot.com/bug?extid=f98189ed18c1f5f32e00 as of linux-next-20250205 .
Anyway, my patch was tested for one month in linux-next tree, and
it seems that no side effect is reported. Please proceed.
next prev parent reply other threads:[~2026-02-07 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 0:26 Viacheslav Dubeyko
2026-02-07 1:18 ` Tetsuo Handa
2026-02-07 8:55 ` John Paul Adrian Glaubitz
2026-02-07 9:44 ` Tetsuo Handa [this message]
2026-02-10 0:50 ` pr-tracker-bot
2026-02-10 11:12 ` Tetsuo Handa
2026-02-10 18:11 ` Viacheslav Dubeyko
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=202dc17c-99dc-4dbd-afae-bb148e7cb025@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mehdi.benhadjkhelifa@gmail.com \
--cc=shardul.b@mpiricsoftware.com \
--cc=slava@dubeyko.com \
--cc=torvalds@linux-foundation.org \
/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®