From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: oe-kbuild-all@lists.linux.dev, Fuad Tabba <tabba@google.com>,
Ackerley Tng <ackerleytng@google.com>,
linux-doc@vger.kernel.org
Subject: [sean-jc:x86/gmem_default_shared 2/10] htmldocs: Documentation/virt/kvm/api.rst:6430: WARNING: Literal block ends without a blank line; unexpected unindent. [docutils]
Date: Tue, 30 Sep 2025 06:02:28 +0200 [thread overview]
Message-ID: <202509300613.3q6FQjEc-lkp@intel.com> (raw)
tree: https://github.com/sean-jc/linux x86/gmem_default_shared
head: 71c8199c17c4609d842dc94e6d225156d8574d82
commit: 65042d91905d173c70a5474c1c032076bbf702dc [2/10] KVM: guest_memfd: Add INIT_SHARED flag, reject user page faults if not set
reproduce: (https://download.01.org/0day-ci/archive/20250930/202509300613.3q6FQjEc-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509300613.3q6FQjEc-lkp@intel.com/
All warnings (new ones prefixed by >>):
ERROR: Cannot find file ./include/linux/mutex.h
ERROR: Cannot find file ./include/linux/mutex.h
WARNING: No kernel-doc for file ./include/linux/mutex.h
ERROR: Cannot find file ./include/linux/fwctl.h
WARNING: No kernel-doc for file ./include/linux/fwctl.h
>> Documentation/virt/kvm/api.rst:6430: WARNING: Literal block ends without a blank line; unexpected unindent. [docutils]
Documentation/virt/kvm/api.rst:6432: WARNING: Literal block expected; none found. [docutils]
vim +6430 Documentation/virt/kvm/api.rst
f844b9053e048e Sean Christopherson 2025-09-29 6419
f844b9053e048e Sean Christopherson 2025-09-29 6420 - GUEST_MEMFD_FLAG_MMAP enables using mmap() on the file descriptor.
f844b9053e048e Sean Christopherson 2025-09-29 6421
65042d91905d17 Sean Christopherson 2025-09-29 6422 - GUEST_MEMFD_FLAG_INIT_SHARED makes all memory in the file shared during
65042d91905d17 Sean Christopherson 2025-09-29 6423 KVM_CREATE_GUEST_MEMFD (memory files created without INIT_SHARED will be
65042d91905d17 Sean Christopherson 2025-09-29 6424 marked private). Shared memory can be faulted into host userspace page
65042d91905d17 Sean Christopherson 2025-09-29 6425 tables. Private memory cannot.
65042d91905d17 Sean Christopherson 2025-09-29 6426
65042d91905d17 Sean Christopherson 2025-09-29 6427 Note! Since KVM doesn't yet support in-place private<=>shared conversions,
65042d91905d17 Sean Christopherson 2025-09-29 6428 INIT_SHARED must be specified in order to fault memory into userspace page
65042d91905d17 Sean Christopherson 2025-09-29 6429 tables. This limitation will go away when in-place conversions are supported.
f844b9053e048e Sean Christopherson 2025-09-29 @6430 ::
3d3a04fad25a66 Fuad Tabba 2025-07-29 6431
:::::: The code at line 6430 was first introduced by commit
:::::: f844b9053e048ebcebbedf37c72d6084a41fa773 KVM: Rework KVM_CAP_GUEST_MEMFD_MMAP into KVM_CAP_GUEST_MEMFD_FLAGS
:::::: TO: Sean Christopherson <seanjc@google.com>
:::::: CC: Sean Christopherson <seanjc@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-30 4:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202509300613.3q6FQjEc-lkp@intel.com \
--to=lkp@intel.com \
--cc=ackerleytng@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.com \
--cc=tabba@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).