Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Larry Bassel <larry.bassel@oracle.com>,
	stable@vger.kernel.org, xieyongji@bytedance.com,
	jasowang@redhat.com, kuba@kernel.org
Subject: Re: [PATCH 5.4.y] virtio-net: Add validation for used length
Date: Tue, 25 Mar 2025 21:17:25 -0400	[thread overview]
Message-ID: <2025032503-payback-shortly-3d1c@gregkh> (raw)
In-Reply-To: <628164ec-d5cf-40c3-b91a-fe557b521321@oracle.com>

On Wed, Mar 26, 2025 at 06:32:19AM +0530, Harshit Mogalapalli wrote:
> Hi Larry,
> 
> 
> On 26/03/25 05:14, Larry Bassel wrote:
> > From: Xie Yongji <xieyongji@bytedance.com>
> > 
> > commit ad993a95c508 ("virtio-net: Add validation for used length")
> > 
> 
> I understand checkpatch.pl warned you, but for stable patches this should
> still be [ Upstream commit ad993a95c508417acdeb15244109e009e50d8758 ]
> 
> Stable maintainers, do you think it is good idea to tweak checkpatch.pl to
> detect these are backports(with help of Upstream commit, commit .. upstream,
> or cherrypicked from lines ?) and it shouldn't warn about long SHA ?

Nope!  Why would you ever run checkpatch on a patch that is already
upstream?

confused,

greg k-h

  reply	other threads:[~2025-03-26  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 23:44 [PATCH 5.4.y] virtio-net: Add validation for used length Larry Bassel
2025-03-26  1:02 ` Harshit Mogalapalli
2025-03-26  1:17   ` Greg KH [this message]
2025-03-26  1:32     ` Harshit Mogalapalli
2025-03-26  1:37       ` Greg KH
2025-03-26  1:45         ` Harshit Mogalapalli
2025-03-26  2:23 ` Sasha Levin

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=2025032503-payback-shortly-3d1c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=larry.bassel@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=xieyongji@bytedance.com \
    /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