public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Li Qiong <liqiong@nfschina.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] mm: slub: fix dereference invalid pointer in alloc_consistency_checks
Date: Fri, 25 Jul 2025 10:52:31 +0800	[thread overview]
Message-ID: <aILxbxcnrd5emETI@eafdfd67401a> (raw)
In-Reply-To: <20250725024854.1201926-1-liqiong@nfschina.com>

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] mm: slub: fix dereference invalid pointer in alloc_consistency_checks
Link: https://lore.kernel.org/stable/20250725024854.1201926-1-liqiong%40nfschina.com

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




  reply	other threads:[~2025-07-25  2:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  2:48 [PATCH] mm: slub: fix dereference invalid pointer in alloc_consistency_checks Li Qiong
2025-07-25  2:52 ` kernel test robot [this message]
2025-07-25  4:01 ` Harry Yoo
2025-07-25  5:46   ` liqiong
2025-07-25  6:49 ` [PATCH v2] mm: slub: avoid deref of free pointer in sanity checks if object is invalid Li Qiong
2025-07-25 16:47   ` Vlastimil Babka
2025-07-25 17:10     ` Matthew Wilcox
2025-07-25 19:22       ` Matthew Wilcox
2025-07-25 22:49         ` Harry Yoo
2025-07-25 19:55       ` Harry Yoo
2025-07-25 23:00         ` Harry Yoo
2025-07-28  2:06           ` liqiong
2025-07-28  3:29             ` Matthew Wilcox
2025-07-28  5:24               ` Harry Yoo
2025-07-28  9:08                 ` liqiong
2025-07-28 13:38                   ` Harry Yoo
2025-07-28  8:52     ` Vlastimil Babka

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=aILxbxcnrd5emETI@eafdfd67401a \
    --to=lkp@intel.com \
    --cc=liqiong@nfschina.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox