linux-kernel - Re: linux-next: build warning after merge of the vfs 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: <20260115150458.4ad09c28@canb.auug.org.au>
Date: Thu, 15 Jan 2026 15:04:58 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Jonathan Corbet
 <corbet@....net>, Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: linux-next: build warning after merge of the vfs tree

Hi Al,

On Thu, 15 Jan 2026 03:10:53 +0000 Al Viro <viro@...iv.linux.org.uk> wrote:
>
> On Thu, Jan 15, 2026 at 02:01:32PM +1100, Stephen Rothwell wrote:
> > 
> > After merging the vfs tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > Documentation/filesystems/porting.rst:1348: ERROR: Unknown target name: "filename". [docutils]
> > 
> > Introduced by commit
> > 
> >   7335480a8461 ("non-consuming variant of do_linkat()")  
> 
> Egads...  That's from "filename_{link,renameat2}()" in there (there's also
> "do_{link,renameat2}()" earlier in the same line, but that didn't produce
> a warning.
> 
> Any suggestions re better way to spell it for .rst?

It eventually becomes (literally) "filename_..." so that might be the
issue.  Maybe quote it like 'function_...()'?

Maybe Jon or Mauro have a suggestion.
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped