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: <2309ca53-a126-881f-1ffa-4f5415a32173@kernel.dk>
Date:   Mon, 27 Mar 2023 12:23:24 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101
 Thunderbird/102.9.0
Subject: Re: [syzbot] Monthly io-uring report
Content-Language: en-US
To:     syzbot <syzbot+lista29bb0eabb2ddbae6f4a@syzkaller.appspotmail.com>,
        io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
        syzkaller-bugs@googlegroups.com
References: <000000000000bb028805f7dfab35@google.com>
From:   Jens Axboe <axboe@kernel.dk>
In-Reply-To: <000000000000bb028805f7dfab35@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 3/27/23 5:01?AM, syzbot wrote:
> 1873    Yes   WARNING in split_huge_page_to_list (2)
>               https://syzkaller.appspot.com/bug?extid=07a218429c8d19b1fb25
> 38      Yes   KASAN: use-after-free Read in nfc_llcp_find_local
>               https://syzkaller.appspot.com/bug?extid=e7ac69e6a5d806180b40

These two are not io_uring. Particularly for the latter, I think syzbot
has a tendency to guess it's io_uring if any kind of task_work is
involved. That means anything off fput ends up in that bucket. Can we
get that improved please?

-- 
Jens Axboe