rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Quaternions <krakow20@gmail.com>
Cc: acourbot@nvidia.com, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] gpu: nova-core: fix bounds check In PmuLookupTableEntry::new, data is sliced from 2..6, but the bounds check data.len() < 5 does not satisfy those bounds.
Date: Fri, 11 Jul 2025 13:54:47 +0200	[thread overview]
Message-ID: <2025071114-unknowing-childlike-4969@gregkh> (raw)
In-Reply-To: <20250711113327.39201-1-krakow20@gmail.com>

On Fri, Jul 11, 2025 at 04:33:26AM -0700, Quaternions wrote:
> Signed-off-by: Rhys Lloyd <krakow20@gmail.com>
> ---
>  drivers/gpu/nova-core/vbios.rs | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I know I can't take patches without a changelog, but perhaps other
maintainers are more lax?

Please don't do this...

And fix your "From:" line in your email client?

thanks,

greg k-h

  parent reply	other threads:[~2025-07-11 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 11:33 [PATCH] gpu: nova-core: fix bounds check In PmuLookupTableEntry::new, data is sliced from 2..6, but the bounds check data.len() < 5 does not satisfy those bounds Quaternions
2025-07-11 11:33 ` [PATCH] gpu: nova-core: define named constants for magic numbers Quaternions
2025-07-11 12:18   ` Alexandre Courbot
2025-07-14 15:26     ` Joel Fernandes
2025-07-11 11:54 ` Greg KH [this message]
2025-07-11 12:04 ` [PATCH] gpu: nova-core: fix bounds check In PmuLookupTableEntry::new, data is sliced from 2..6, but the bounds check data.len() < 5 does not satisfy those bounds Alexandre Courbot
2025-07-11 12:20   ` Alexandre Courbot
2025-07-11 14:32     ` Rhys Lloyd
2025-07-11 14:55       ` Miguel Ojeda
2025-07-11 12:12 ` Miguel Ojeda

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=2025071114-unknowing-childlike-4969@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=acourbot@nvidia.com \
    --cc=krakow20@gmail.com \
    --cc=rust-for-linux@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;
as well as URLs for NNTP newsgroup(s).