Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <a2596c0a-ad77-d70d-0b26-5d2ff01d1857@I-love.SAKURA.ne.jp>
Date:   Sat, 8 Jul 2023 21:45:05 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: [syzbot] [tomoyo?] [hfs?] general protection fault in
 tomoyo_check_acl (3)
Content-Language: en-US
From:   Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To:     syzbot <syzbot+28aaddd5a3221d7fd709@syzkaller.appspotmail.com>,
        syzkaller-bugs@googlegroups.com
Cc:     linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
References: <000000000000fcfb4a05ffe48213@google.com>
 <8bacb159-6512-b2d0-d015-a9c4f141df8b@I-love.SAKURA.ne.jp>
In-Reply-To: <8bacb159-6512-b2d0-d015-a9c4f141df8b@I-love.SAKURA.ne.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2023/07/08 20:29, Tetsuo Handa wrote:
> This is not a bug in TOMOYO, for booting with security=none results in crashing at other locations.
> 
> This might be a bug in HFS's error handling. But since there are several bugs
> which have been added as "mm" in the last few days, let's change this as "mm".
> 
> #syz set subsystems: mm
> 

Bisect log says that 6.3 and 6.4 crashed similarly. Thus, assume that this is a HFS problem.

#syz set subsystems: hfs