[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202dc17c-99dc-4dbd-afae-bb148e7cb025@I-love.SAKURA.ne.jp>
Date: Sat, 7 Feb 2026 18:44:52 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Viacheslav Dubeyko <slava@...eyko.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
frank.li@...o.com, jkoolstra@...all.nl, mehdi.benhadjkhelifa@...il.com,
shardul.b@...ricsoftware.com, torvalds@...ux-foundation.org
Subject: Re: [GIT PULL] hfs/hfsplus changes for 7.0-rc1
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.
Powered by blists - more mailing lists