From: Kees Cook <kees@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH 3/3] overflow: add range_overflows() and range_end_overflows()
Date: Thu, 4 Sep 2025 09:27:50 -0700 [thread overview]
Message-ID: <202509040927.30BEE17@keescook> (raw)
In-Reply-To: <eb4a61f86330afe95e232cc515f117ed602e108d@intel.com>
On Thu, Sep 04, 2025 at 10:34:04AM +0300, Jani Nikula wrote:
> On Wed, 03 Sep 2025, Kees Cook <kees@kernel.org> wrote:
> > On Fri, Aug 29, 2025 at 08:46:01PM +0300, Jani Nikula wrote:
> >> Move the range_overflows() and range_end_overflows() along with the _t
> >> variants over from drm/i915 and drm/buddy to overflow.h.
> >>
> >> Cc: Kees Cook <kees@kernel.org>
> >> Cc: Gustavo A. R. Silva <gustavoars@kernel.org>
> >> Cc: linux-hardening@vger.kernel.org
> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Looks good to me! :)
> >
> > Reviewed-by: Kees Cook <kees@kernel.org>
>
> Cool, thanks! How do you want to handle merging this?
Since it's touching drm, feel free to take it there. I'm not worried
about conflict resolution in overflow.h.
--
Kees Cook
next prev parent reply other threads:[~2025-09-04 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 17:45 [PATCH 1/3] drm/i915: rename range_overflows_end() to range_end_overflows() Jani Nikula
2025-08-29 17:46 ` [PATCH 2/3] drm/i915: document range_overflows() and range_end_overflows() macros Jani Nikula
2025-09-08 12:27 ` Hogander, Jouni
2025-08-29 17:46 ` [PATCH 3/3] overflow: add range_overflows() and range_end_overflows() Jani Nikula
2025-09-04 2:43 ` Kees Cook
2025-09-04 7:34 ` Jani Nikula
2025-09-04 16:27 ` Kees Cook [this message]
2025-09-08 12:43 ` Jani Nikula
2025-09-08 12:28 ` Hogander, Jouni
2025-09-03 10:03 ` [PATCH 1/3] drm/i915: rename range_overflows_end() to range_end_overflows() Hogander, Jouni
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=202509040927.30BEE17@keescook \
--to=kees@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@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