From: kernel test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH][RFC][CFT] use uniform permission checks for all mount propagation changes
Date: Thu, 14 Aug 2025 13:52:55 +0800 [thread overview]
Message-ID: <aJ15t0tdVvMkin4h@1a863d778a0f> (raw)
In-Reply-To: <20250814055142.GN222315@ZenIV>
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-1
Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
Subject: [PATCH][RFC][CFT] use uniform permission checks for all mount propagation changes
Link: https://lore.kernel.org/stable/20250814055142.GN222315%40ZenIV
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-14 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANaxB-xXgW1FEj6ydBT2=cudTbP=fX6x8S53zNkWcw1poL=L2A@mail.gmail.com>
[not found] ` <20250724230052.GW2580412@ZenIV>
2025-07-26 17:12 ` do_change_type(): refuse to operate on unmounted/not ours mounts Andrei Vagin
2025-07-26 17:53 ` Al Viro
2025-07-26 21:01 ` Andrei Vagin
2025-07-31 2:40 ` Pavel Tikhomirov
2025-07-31 7:53 ` Christian Brauner
2025-07-31 8:11 ` Pavel Tikhomirov
2025-08-13 18:56 ` Al Viro
2025-08-13 19:09 ` Tycho Andersen
2025-08-13 19:41 ` Al Viro
2025-08-14 4:08 ` Pavel Tikhomirov
2025-08-14 4:42 ` Al Viro
2025-08-14 5:51 ` [PATCH][RFC][CFT] use uniform permission checks for all mount propagation changes Al Viro
2025-08-14 5:52 ` kernel test robot [this message]
2025-08-14 5:57 ` [RFC][CFT] selftest for permission checks in " Al Viro
2025-08-14 6:37 ` Al Viro
2025-08-14 7:07 ` do_change_type(): refuse to operate on unmounted/not ours mounts Pavel Tikhomirov
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=aJ15t0tdVvMkin4h@1a863d778a0f \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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