From: "Mickaël Salaün" <mic@digikod.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
Matthieu Buffet <matthieu@buffet.re>,
oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [mic:next 15/15] htmldocs: Documentation/userspace-api/landlock.rst:768: WARNING: Inline interpreted text or phrase reference start-string without end-string. [docutils]
Date: Fri, 12 Jun 2026 19:35:05 +0200 [thread overview]
Message-ID: <20260612.waicoh3ohF5e@digikod.net> (raw)
In-Reply-To: <1cc99145-0316-44f5-b134-2b4f90b326c4@infradead.org>
On Fri, Jun 12, 2026 at 08:35:57AM -0700, Randy Dunlap wrote:
>
>
> On 6/12/26 12:52 AM, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git next
> > head: a6f0a6f5377fae42a8028f63c89d544c68f24b60
> > commit: a6f0a6f5377fae42a8028f63c89d544c68f24b60 [15/15] landlock: Add documentation for UDP support
> > compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
> > docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
> > reproduce: (https://download.01.org/0day-ci/archive/20260612/202606120923.1nYYlfdb-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/202606120923.1nYYlfdb-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > Scope flags
> > ~~~~~~~~~~~ [docutils]
> >>> Documentation/userspace-api/landlock.rst:768: WARNING: Inline interpreted text or phrase reference start-string without end-string. [docutils]
> >>> Documentation/userspace-api/landlock.rst:768: WARNING: Inline interpreted text or phrase reference start-string without end-string. [docutils]
> > Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:40: ERROR: Unknown target name: "filesystem flags". [docutils]
> > Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:45: ERROR: Unknown target name: "network flags". [docutils]
> > Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:50: 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:168: ERROR: Unknown target name: "filesystem flags". [docutils]
> >
> >
>
> In case it's not obvious:
>
> > vim +768 Documentation/userspace-api/landlock.rst
> >
> > 767
> > > 768 Starting with the Landlock ABI version 10, it is possible to restrict
> > 769 setting the local port of UDP sockets with the
> > 770 ``LANDLOCK_ACCESS_NET_BIND_UDP`` right. This includes restricting the
> > 771 ability to trigger autobind of an ephemeral port by the kernel by e.g.
> > 772 sending a first datagram or setting the remote peer of a socket.
> > 773 The ``LANDLOCK_ACCESS_NET_CONNECT_SEND_UDP`` right controls setting the
> > 774 remote port of UDP sockets (via :manpage:`connect(2)), and sending
>
> missing ending `
Thanks, fixed!
>
> > 775 datagrams to an explicit remote port (ignoring any destination set on
> > 776 UDP sockets, via e.g. :manpage:`sendto(2)).
>
> same here
>
> > 777
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
> >
>
> --
> ~Randy
>
prev parent reply other threads:[~2026-06-12 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 7:52 [mic:next 15/15] htmldocs: Documentation/userspace-api/landlock.rst:768: WARNING: Inline interpreted text or phrase reference start-string without end-string. [docutils] kernel test robot
2026-06-12 15:35 ` Randy Dunlap
2026-06-12 17:35 ` Mickaël Salaün [this message]
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=20260612.waicoh3ohF5e@digikod.net \
--to=mic@digikod.net \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matthieu@buffet.re \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
/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.