Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Rongwei Wang <rongwei.wang@linux.alibaba.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()
Date: Sun, 2 Apr 2023 06:20:08 +0800	[thread overview]
Message-ID: <ZCiuGEkyk/1Afisk@ec83ac1404bb> (raw)
In-Reply-To: <20230401221920.57986-1-rongwei.wang@linux.alibaba.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] mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()
Link: https://lore.kernel.org/stable/20230401221920.57986-1-rongwei.wang%40linux.alibaba.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://github.com/intel/lkp-tests




       reply	other threads:[~2023-04-01 22:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230401221920.57986-1-rongwei.wang@linux.alibaba.com>
2023-04-01 22:20 ` kernel test robot [this message]
     [not found] ` <ZCpRtASqL5z5QphY@casper.infradead.org>
2023-04-03  8:02   ` [PATCH] mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() Rongwei Wang
2023-04-04 15:47 ` [PATCH v2] " Rongwei Wang
2023-04-04 16:08   ` Rongwei Wang
2023-04-06 12:12     ` Aaron Lu
2023-04-06 12:55       ` Rongwei Wang
2023-04-04 19:26   ` Andrew Morton
2023-04-05  6:49     ` Rongwei Wang
2023-04-06  6:58     ` Aaron Lu
2023-04-06 12:20       ` Rongwei Wang
2023-04-06 14:04   ` Aaron Lu
2023-04-06 14:57     ` Aaron Lu
2023-04-07  2:20       ` Rongwei Wang

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=ZCiuGEkyk/1Afisk@ec83ac1404bb \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rongwei.wang@linux.alibaba.com \
    --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