linux-kernel - Re: linux-next: build warning after merge of the kvm 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: <3cfe0285-bf5a-4a0b-ae72-f5008c71d28e@redhat.com>
Date:   Tue, 14 Nov 2023 13:50:30 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>, KVM <kvm@...r.kernel.org>
Cc:     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 kvm tree

On 11/14/23 04:13, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the kvm tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> Documentation/filesystems/api-summary:74: fs/anon_inodes.c:167: ERROR: Unexpected indentation.
> Documentation/filesystems/api-summary:74: fs/anon_inodes.c:168: WARNING: Block quote ends without a blank line; unexpected unindent.

This reproduces with the version of sphinx in
Documentation/sphinx/requirements.txt.  The fix is
simply this, for which I will send a patch:

diff --git a/fs/anon_inodes.c b/fs/anon_inodes.c
index e02f4e2e2ece..0496cb5b6eab 100644
--- a/fs/anon_inodes.c
+++ b/fs/anon_inodes.c
@@ -163,8 +163,10 @@ EXPORT_SYMBOL_GPL(anon_inode_getfile);
   *
   * Create a new anonymous inode and file pair.  This can be done for two
   * reasons:
+ *
   * - for the inode to have its own security context, so that LSMs can enforce
   *   policy on the inode's creation;
+ *
   * - if the caller needs a unique inode, for example in order to customize
   *   the size returned by fstat()
   *
@@ -250,8 +252,10 @@ EXPORT_SYMBOL_GPL(anon_inode_getfd);
   *
   * Create a new anonymous inode and file pair.  This can be done for two
   * reasons:
+ *
   * - for the inode to have its own security context, so that LSMs can enforce
   *   policy on the inode's creation;
+ *
   * - if the caller needs a unique inode, for example in order to customize
   *   the size returned by fstat()
   *

Paolo