From: kernel test robot <lkp@intel.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v5 1/2] lib/mpi: Fix buffer overrun when SG is too long
Date: Tue, 27 Dec 2022 22:29:03 +0800 [thread overview]
Message-ID: <Y6sBL789NM3i3nJL@181616e551cc> (raw)
In-Reply-To: <20221227142740.2807136-2-roberto.sassu@huaweicloud.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 v5 1/2] lib/mpi: Fix buffer overrun when SG is too long
Link: https://lore.kernel.org/stable/20221227142740.2807136-2-roberto.sassu%40huaweicloud.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
next prev parent reply other threads:[~2022-12-27 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 14:27 [PATCH v5 0/2] KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() Roberto Sassu
2022-12-27 14:27 ` [PATCH v5 1/2] lib/mpi: Fix buffer overrun when SG is too long Roberto Sassu
2022-12-27 14:29 ` kernel test robot [this message]
2022-12-29 22:38 ` Eric Biggers
2022-12-30 13:35 ` David Laight
2022-12-30 15:39 ` Herbert Xu
2022-12-31 13:23 ` David Laight
2023-01-06 15:18 ` Herbert Xu
2023-01-16 8:57 ` Roberto Sassu
2023-01-16 9:06 ` Herbert Xu
2023-01-20 10:23 ` Roberto Sassu
2022-12-27 14:27 ` [PATCH v5 2/2] KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() Roberto Sassu
2022-12-29 22:39 ` Eric Biggers
2023-01-27 8:27 ` Roberto Sassu
2023-02-09 10:49 ` Roberto Sassu
2023-02-09 18:53 ` Eric Biggers
2023-02-09 22:46 ` Paul Moore
2023-02-10 3:56 ` Jarkko Sakkinen
2023-02-10 17:32 ` Paul Moore
2023-02-10 3:52 ` Jarkko Sakkinen
2023-05-26 7:35 ` Roberto Sassu
2023-06-01 21:00 ` Stefan Berger
2023-06-02 9:17 ` Roberto Sassu
2023-06-02 13:17 ` Eric Biggers
2023-06-02 13:39 ` Roberto Sassu
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=Y6sBL789NM3i3nJL@181616e551cc \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roberto.sassu@huaweicloud.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