linux-kernel - Re: linux-next: build warning after merge of the mm-stable 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJuCfpFkPvyDLNxjQ1bJS=fQds-mUS=+e-ZKf00nSQ5OyohhRg@mail.gmail.com>
Date: Thu, 16 Jan 2025 07:10:32 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-stable tree

On Wed, Jan 15, 2025 at 10:05 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the mm-stable tree, today's linux-next build (htmldocs)
> produced this warning:
>
> include/linux/seqlock.h:341: warning: Function parameter or struct member 'start' not described in 'raw_seqcount_try_begin'

Oops. Thanks for catching this! It should be:

@start: count to be passed to read_seqcount_retry()

Should I send a fixup to Andrew for inclusion into the mm tree?

>
> Introduced by commit
>
>   dba4761a3e40 ("seqlock: add raw_seqcount_try_begin")
>
> I seem to have missed this when it was first introduced, sorry.
>
> --
> Cheers,
> Stephen Rothwell