From: Pratyush Yadav <ptyadav@amazon.de>
To: kernel test robot <lkp@intel.com>
Cc: <stable@vger.kernel.org>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [PATCH 5.4] cifs/smb3: Fix NULL pointer dereference in smb2_query_info_compound()
Date: Wed, 5 Apr 2023 13:47:52 +0200 [thread overview]
Message-ID: <mafs0o7o2h7o7.fsf@amazon.de> (raw)
In-Reply-To: <ZC1fJiHvpbXcysXi@ec83ac1404bb> (kernel test robot's message of "Wed, 5 Apr 2023 19:44:38 +0800")
On Wed, Apr 05 2023, kernel test robot wrote:
> 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.'
I think the robot should also learn to look at the 'To:' header :-)
> Subject: [PATCH 5.4] cifs/smb3: Fix NULL pointer dereference in smb2_query_info_compound()
> Link: https://lore.kernel.org/stable/20230405114220.108739-1-ptyadav%40amazon.de
>
> The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
--
Regards,
Pratyush Yadav
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2023-04-05 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 11:42 [PATCH 5.4] cifs/smb3: Fix NULL pointer dereference in smb2_query_info_compound() Pratyush Yadav
2023-04-05 11:44 ` kernel test robot
2023-04-05 11:47 ` Pratyush Yadav [this message]
2023-04-05 12:26 ` Greg KH
2023-04-05 12:26 ` Greg KH
2023-04-05 13:33 ` Pratyush Yadav
2023-04-05 14:22 ` Greg KH
2023-04-12 7:47 ` Yujie Liu
2023-04-12 13:21 ` Pratyush Yadav
2023-04-13 5:49 ` Yujie Liu
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=mafs0o7o2h7o7.fsf@amazon.de \
--to=ptyadav@amazon.de \
--cc=lkp@intel.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.