All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chun-Yi Lee <joeyli.kernel@gmail.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2] aoe: fix the potential use-after-free problem in more places
Date: Tue, 25 Jun 2024 18:48:45 +0800	[thread overview]
Message-ID: <ZnqgjecCOeiE671O@6715f18d4702> (raw)
In-Reply-To: <20240624064418.27043-1-jlee@suse.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 v2] aoe: fix the potential use-after-free problem in more places
Link: https://lore.kernel.org/stable/20240624064418.27043-1-jlee%40suse.com

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




  parent reply	other threads:[~2024-06-25 10:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24  6:44 [PATCH v2] aoe: fix the potential use-after-free problem in more places Chun-Yi Lee
2024-06-24  7:05 ` Greg KH
2024-06-24 11:00   ` joeyli
2024-06-24  8:40 ` Markus Elfring
2024-06-24 11:01   ` joeyli
2024-06-24 11:43     ` Markus Elfring
2024-06-24 11:54       ` joeyli
2024-06-24 12:45         ` Greg KH
2024-06-24  9:27 ` Markus Elfring
2024-06-24 11:04   ` joeyli
2024-06-24 11:28     ` Markus Elfring
2024-06-24 11:45       ` joeyli
2024-06-25 10:48 ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-12 10:29 Chun-Yi Lee
2024-09-12 10:58 ` Valentin Kleibel
2024-09-16  9:23   ` joeyli
2024-10-02  5:53   ` joeyli
2024-11-04 13:38     ` Valentin Kleibel
2024-11-11 13:53       ` joeyli
2024-09-12 11:01 ` Greg KH
2024-06-13  4:15 Chun-Yi Lee
2024-05-14 15:18 Chun-Yi Lee
2024-05-14 15:34 ` Markus Elfring
2024-05-15  5:09   ` joeyli

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=ZnqgjecCOeiE671O@6715f18d4702 \
    --to=lkp@intel.com \
    --cc=joeyli.kernel@gmail.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 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.