From: kernel test robot <lkp@intel.com>
To: Mahmoud Adam <mngyadam@amazon.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 5.4/5.10/5.15] cifs: Fix buffer overflow when parsing NFS reparse points
Date: Mon, 25 Nov 2024 10:23:49 +0800 [thread overview]
Message-ID: <Z0PftUzqwoftS1ri@ca93ea81d97d> (raw)
In-Reply-To: <20241122152943.76044-1-mngyadam@amazon.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-3
Rule: The upstream commit ID must be specified with a separate line above the commit text.
Subject: [PATCH 5.4/5.10/5.15] cifs: Fix buffer overflow when parsing NFS reparse points
Link: https://lore.kernel.org/stable/20241122152943.76044-1-mngyadam%40amazon.com
Please ignore this mail if the patch is not relevant for upstream.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-25 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 15:29 [PATCH 5.4/5.10/5.15] cifs: Fix buffer overflow when parsing NFS reparse points Mahmoud Adam
2024-11-22 19:26 ` Sasha Levin
2024-11-25 2:23 ` kernel test robot [this message]
2024-11-25 8:55 ` Mahmoud Adam
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=Z0PftUzqwoftS1ri@ca93ea81d97d \
--to=lkp@intel.com \
--cc=mngyadam@amazon.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.