All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Varsha Teratipally <teratipally@google.com>
Cc: stable@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH] xfs: fix up non-directory creation in SGID directories
Date: Wed, 7 Sep 2022 02:37:36 +0800	[thread overview]
Message-ID: <YxeTcCVHwVfLW1yL@facefcfb2e4a> (raw)
In-Reply-To: <20220906183600.1926315-2-teratipally@google.com>

Hi,

Thanks for your patch.

FYI: kernel test robot notices the stable kernel rule is not satisfied.

Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
Subject: [PATCH] xfs: fix up non-directory creation in SGID directories
Link: https://lore.kernel.org/stable/20220906183600.1926315-2-teratipally%40google.com

The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp




  reply	other threads:[~2022-09-06 18:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 18:35 Request to cherry-pick 01ea173e103edd5ec41acec65b9261b87e123fc2 to v5.10 Varsha Teratipally
2022-09-06 18:36 ` [PATCH] xfs: fix up non-directory creation in SGID directories Varsha Teratipally
2022-09-06 18:37   ` kernel test robot [this message]
2022-09-07  7:40   ` Amir Goldstein
2022-09-07  7:43     ` Amir Goldstein
2022-09-08 11:48   ` Greg KH
2022-09-08 12:02     ` Amir Goldstein
2022-09-14 16:39       ` Darrick J. Wong
2022-09-07  7:46 ` Request to cherry-pick 01ea173e103edd5ec41acec65b9261b87e123fc2 to v5.10 Amir Goldstein
  -- strict thread matches above, loose matches on Subject: below --
2021-01-13 18:46 [PATCH] xfs: fix up non-directory creation in SGID directories Christoph Hellwig
2021-01-14 10:45 ` Christian Brauner
2021-01-14 16:06   ` Darrick J. Wong
2021-01-14 16:37     ` Christian Brauner

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=YxeTcCVHwVfLW1yL@facefcfb2e4a \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=stable@vger.kernel.org \
    --cc=teratipally@google.com \
    /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.