nouveau.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Quaternions" <krakow20@gmail.com>
Cc: <nouveau@lists.freedesktop.org>, <acourbot@nvidia.com>
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 20:03:43 +0200	[thread overview]
Message-ID: <DB9F9VX833TY.1UG2ZE2K2ZGNQ@kernel.org> (raw)
In-Reply-To: <20250711093015.28785-1-krakow20@gmail.com>

Hi Rhys,

On Fri Jul 11, 2025 at 11:30 AM CEST, Quaternions wrote:
> Signed-off-by: Rhys Lloyd <krakow20@gmail.com>

Thanks for your contribution.

When sending patches, please make sure to follow the kernel's patch submission
guidelines [1].

In particular, please stick to short and meaningful commit subject, followed by
a commit description, even if the patch is simple and obvious.

Also make sure to run ./scripts/checkpatch.pl and ./scripts/get_maintainer.pl to
get your patches checked and find the correct list of people to send them to.

Finally, please also consider the Rust submit checklist [2].

Thanks,
Danilo

[1] https://docs.kernel.org/process/submitting-patches.html
[2] https://rust-for-linux.com/contributing#submit-checklist-addendum

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  9:30 [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  9:30 ` [PATCH] gpu: nova-core: define named constants for magic numbers Quaternions
2025-07-11 18:03 ` Danilo Krummrich [this message]
2025-07-12  1:30   ` [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 Rhys Lloyd
2025-07-12 13:11     ` Danilo Krummrich

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=DB9F9VX833TY.1UG2ZE2K2ZGNQ@kernel.org \
    --to=dakr@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=krakow20@gmail.com \
    --cc=nouveau@lists.freedesktop.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).