linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Günther Noack" <gnoack@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Mickaël Salaün" <mic@digikod.net>,
	linux-doc@vger.kernel.org
Subject: [linux-next:master 1819/1905] htmldocs: ./security/landlock/ruleset.h:287: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Fri, 17 Nov 2023 21:07:36 +0800	[thread overview]
Message-ID: <202311172010.AfFjwTiU-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   eff99d8edbed7918317331ebd1e365d8e955d65e
commit: f3672f581e951204d0ff4570a04daef1b81e182c [1819/1905] landlock: Add IOCTL access right
reproduce: (https://download.01.org/0day-ci/archive/20231117/202311172010.AfFjwTiU-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/202311172010.AfFjwTiU-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> ./security/landlock/ruleset.h:287: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst

vim +287 ./security/landlock/ruleset.h

   285	
   286	/**
 > 287	 * Returns @access with the synthetic IOCTL group flags enabled if necessary.
   288	 *
   289	 * @handled: Handled FS access rights.
   290	 * @access:  FS access rights to expand.
   291	 *
   292	 * Returns:
   293	 * @access expanded by the necessary flags for the synthetic IOCTL access rights.
   294	 */
   295	static inline access_mask_t expand_all_ioctl(access_mask_t handled,
   296						     access_mask_t access)
   297	{
   298		return access |
   299		       expand_ioctl(handled, access, LANDLOCK_ACCESS_FS_WRITE_FILE,
   300				    IOCTL_CMD_G1 | IOCTL_CMD_G2 | IOCTL_CMD_G4) |
   301		       expand_ioctl(handled, access, LANDLOCK_ACCESS_FS_READ_FILE,
   302				    IOCTL_CMD_G1 | IOCTL_CMD_G2 | IOCTL_CMD_G3) |
   303		       expand_ioctl(handled, access, LANDLOCK_ACCESS_FS_READ_DIR,
   304				    IOCTL_CMD_G1);
   305	}
   306	

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


                 reply	other threads:[~2023-11-17 13:08 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=202311172010.AfFjwTiU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gnoack@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mic@digikod.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox