From: kernel test robot <lkp@intel.com>
To: Mathura_Kumar <academic1mathura@gmail.com>, brauner@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, academic1mathura@gmail.com,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH] mqueue: introduce new do_mq_timedreceive2() [ mq_peek syscall] for non-destructive receive and inspection,fix minor issue,prepared doc.
Date: Thu, 5 Mar 2026 13:48:00 +0100 [thread overview]
Message-ID: <202603051326.wnlF51YD-lkp@intel.com> (raw)
In-Reply-To: <20260305065212.83213-1-academic1mathura@gmail.com>
Hi Mathura_Kumar,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes brauner-vfs/vfs.all linus/master v7.0-rc2 next-20260304]
[cannot apply to tip/x86/asm]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Mathura_Kumar/mqueue-introduce-new-do_mq_timedreceive2-mq_peek-syscall-for-non-destructive-receive-and-inspection-fix-minor-issue-prep/20260305-145412
base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link: https://lore.kernel.org/r/20260305065212.83213-1-academic1mathura%40gmail.com
patch subject: [PATCH] mqueue: introduce new do_mq_timedreceive2() [ mq_peek syscall] for non-destructive receive and inspection,fix minor issue,prepared doc.
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260305/202603051326.wnlF51YD-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/202603051326.wnlF51YD-lkp@intel.com/
All warnings (new ones prefixed by >>):
Documentation/userspace-api/landlock:526: ./include/uapi/linux/landlock.h:45: ERROR: Unknown target name: "network flags". [docutils]
Documentation/userspace-api/landlock:526: ./include/uapi/linux/landlock.h:50: ERROR: Unknown target name: "scope flags". [docutils]
Documentation/userspace-api/landlock:526: ./include/uapi/linux/landlock.h:24: ERROR: Unknown target name: "filesystem flags". [docutils]
Documentation/userspace-api/landlock:535: ./include/uapi/linux/landlock.h:166: ERROR: Unknown target name: "filesystem flags". [docutils]
Documentation/userspace-api/landlock:535: ./include/uapi/linux/landlock.h:189: ERROR: Unknown target name: "network flags". [docutils]
>> Documentation/userspace-api/syscall.rst:88: WARNING: Inline emphasis start-string without end-string. [docutils]
>> Documentation/userspace-api/syscall.rst:88: WARNING: Inline emphasis start-string without end-string. [docutils]
>> Documentation/userspace-api/syscall.rst:91: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/userspace-api/syscall.rst:94: WARNING: Inline emphasis start-string without end-string. [docutils]
Documentation/userspace-api/syscall.rst:94: WARNING: Inline emphasis start-string without end-string. [docutils]
Documentation/userspace-api/syscall.rst:110: ERROR: Unexpected indentation. [docutils]
>> Documentation/userspace-api/syscall.rst:111: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/userspace-api/syscall.rst:145: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/userspace-api/syscall.rst:181: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
>> Documentation/userspace-api/syscall.rst: WARNING: document isn't included in any toctree [toc.not_included]
Documentation/networking/skbuff:36: ./include/linux/skbuff.h:181: WARNING: Failed to create a cross reference. A title or caption not found: 'crc' [ref.ref]
vim +88 Documentation/userspace-api/syscall.rst
79
80 NAME
81 mq_timedreceive2 - receive or peek at a message from a
82 POSIX message queue
83
84 SYNOPSIS
85 #include <mqueue.c>
86
87 struct mq_timedreceive2_args {
> 88 size_t msg_len;
89 unsigned int *msg_prio;
90 char *msg_ptr;
> 91 };
92
93 ssize_t mq_timedreceive2(mqd_t mqdes,
94 struct mq_timedreceive2_args *uargs,
95 unsigned int flags,
96 unsigned long index,
97 const struct timespec *abs_timeout);
98
99 Note: As of now,no glibc wrapper exists for this syscall. Callers must
100 invoke it directly using syscall().
101
102 DESCRIPTION
103 mq_timedreceive2() receives or peeks at a message from the
104 message queue referred to by the descriptor mqdes.
105
106 The uargs structure provides the message buffer parameters:
107
108 msg_ptr userspace buffer to receive the message body
109 msg_len size of msg_ptr in bytes, must be >= mq_msgsize
110 of the queue
> 111 msg_prio if not NULL, the priority of the received message
112 is stored here
113
114 The flags argument controls receive behavior. The following
115 flags are defined:
116
117 MQ_PEEK
118 Copy the message into msg_ptr without removing it
119 from the queue. The queue is not modified. If this
120 flag is not set, behavior is identical to
121 mq_timedreceive() and the message is consumed.
122
123 The index argument selects which message to operate on within
124 the priority-ordered queue. index 0 refers to the highest
125 priority message. When MQ_PEEK is not set, index will be ignored but must be 0.
126
127 The abs_timeout argument specifies an absolute timeout. If
128 MQ_PEEK is set,this take control to peek path and so timeout
129 will be ignored otherwise it will behave as mq_timedreceive().
130
131
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-05 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 6:52 [PATCH] mqueue: introduce new do_mq_timedreceive2() [ mq_peek syscall] for non-destructive receive and inspection,fix minor issue,prepared doc Mathura_Kumar
2026-03-05 12:48 ` kernel test robot [this message]
2026-03-05 14:39 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2026-03-05 18:09 Mathura_Kumar
2026-03-06 0:03 ` Randy Dunlap
2026-03-06 10:36 ` kernel test robot
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=202603051326.wnlF51YD-lkp@intel.com \
--to=lkp@intel.com \
--cc=academic1mathura@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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