All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Cong Wang <cwang@multikernel.io>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
	linux-doc@vger.kernel.org
Subject: htmldocs: Documentation/userspace-api/seccomp_filter.rst:330: WARNING: Inline literal start-string without end-string. [docutils]
Date: Sun, 05 Jul 2026 05:43:16 +0200	[thread overview]
Message-ID: <202607050546.ql206lFF-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Cong-Wang/mm-add-__do_mmap-and-vm_mmap_remote-vm_munmap_remote/20260705-072005
head:   6fe40c9ec33b138a8d0a62b0750144d8384a7215
commit: 6030255b582d365ac34a1e512ae5ec9f44751391 docs/seccomp: document pinned-memfd redirect ioctls
date:   4 hours ago
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260705/202607050546.ql206lFF-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/202607050546.ql206lFF-lkp@intel.com/

All warnings (new ones prefixed by >>):

   Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:58: ERROR: Unknown target name: "network flags". [docutils]
   Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:63: ERROR: Unknown target name: "scope flags". [docutils]
   Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:24: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:605: ./include/uapi/linux/landlock.h:228: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:605: ./include/uapi/linux/landlock.h:251: ERROR: Unknown target name: "network flags". [docutils]
>> Documentation/userspace-api/seccomp_filter.rst:330: WARNING: Inline literal start-string without end-string. [docutils]
   Documentation/networking/checksum-offloads:157: ./include/linux/skbuff.h:181: WARNING: Failed to create a cross reference. A title or caption not found: 'crc' [ref.ref]


vim +330 Documentation/userspace-api/seccomp_filter.rst

   320	
   321	    struct seccomp_notif_pin_install {
   322	        __u64 id;
   323	        __u32 flags;       /* reserved, must be 0 */
   324	        __u32 memfd;
   325	        __u64 target_addr;
   326	        __u64 size;
   327	        __u64 offset;      /* page-aligned offset into memfd */
   328	    };
   329	
 > 330	``id`` names an active notification (the trapped task to install into).
   331	``target_addr``, ``size`` and ``offset`` are page-aligned; ``offset`` selects
   332	where in ``memfd`` the mapping starts, so one memfd can back several pins. If
   333	``target_addr`` is ``0`` the kernel picks a free address and writes it back;
   334	otherwise an existing mapping there yields ``-EEXIST``. The pin is read-only
   335	and sealed, the target and its threads cannot unmap, move, reprotect or
   336	overwrite it, and lasts until the target ``execve()``s or exits.
   337	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-05  3:43 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=202607050546.ql206lFF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cwang@multikernel.io \
    --cc=linux-doc@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.