linux-kernel - Re: linux-next: build warnings after merge of the block tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4af8d410-9930-44e9-b558-7ce6420f3d96@kernel.dk>
Date: Thu, 3 Oct 2024 06:31:35 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Keith Busch <kbusch@...nel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the block tree

On 10/2/24 9:18 PM, Stephen Rothwell wrote:
> Hi All,
> 
> On Fri, 27 Sep 2024 04:20:40 -0600 Jens Axboe <axboe@...nel.dk> wrote:
>>
>> On 9/26/24 9:43 PM, Stephen Rothwell wrote:
>>>
>>> On Mon, 16 Sep 2024 18:36:22 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:  
>>>>
>>>> After merging the block tree, today's linux-next build (htmldocs)
>>>> produced these warnings:
>>>>
>>>> block/blk-integrity.c:69: warning: Function parameter or struct member 'rq' not described in 'blk_rq_map_integrity_sg'
>>>> block/blk-integrity.c:69: warning: Excess function parameter 'q' description in 'blk_rq_map_integrity_sg'
>>>> block/blk-integrity.c:69: warning: Excess function parameter 'bio' description in 'blk_rq_map_integrity_sg'
>>>>
>>>> Introduced by commit
>>>>
>>>>   76c313f658d2 ("blk-integrity: improved sg segment mapping")  
>>>
>>> I am still seeing those warnings.  
>>
>> Due to travel, didn't get it queued up before just now.
> 
> These warnings have reappeared today :-(

It's because that fix is headed upstream today, and I re-did my for-next
tree and didn't include bits headed to 6.12. I'll pull them back, but in
any case, it'll go away in my tree (and master) shortly.

-- 
Jens Axboe