From: Kees Cook <keescook@chromium.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Jani Nikula" <jani.nikula@intel.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Lyude Paul" <lyude@redhat.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Dave Airlie" <airlied@redhat.com>,
"Douglas Anderson" <dianders@chromium.org>,
"Ankit Nautiyal" <ankit.k.nautiyal@intel.com>,
"Uma Shankar" <uma.shankar@intel.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 0/2] drm/dp: Fix out-of-bounds reads
Date: Sun, 27 Feb 2022 10:55:08 -0800 [thread overview]
Message-ID: <202202271053.91D3CE109@keescook> (raw)
In-Reply-To: <YhihqzqPW7qbYnB9@orome>
On Fri, Feb 25, 2022 at 10:30:19AM +0100, Thierry Reding wrote:
> On Thu, Feb 24, 2022 at 07:56:08PM -0800, Kees Cook wrote:
> > Hi,
> >
> > I'm sending these again, as they still need fixing. They have been
> > rebased due to the drm_dp_helper code being moved into a subdirectory.
>
> Yeah, I noticed the other day that this had been partially reverted by
> the DP code move. I've applied this now, though it didn't apply cleanly,
> so I'll do a couple of test builds to make sure my resolution is correct
> and will push this out later on.
Awesome; thank you!
Yeah, I had based on drm/drm-next rather than drm-misc/drm-misc-next. I
wasn't sure which tree I needed to base on after the files moved.
FWIW, the resulting patches look good to me. Thanks for fixing them up!
-Kees
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Douglas Anderson <dianders@chromium.org>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Jani Nikula <jani.nikula@intel.com>,
Uma Shankar <uma.shankar@intel.com>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-tegra@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 0/2] drm/dp: Fix out-of-bounds reads
Date: Sun, 27 Feb 2022 10:55:08 -0800 [thread overview]
Message-ID: <202202271053.91D3CE109@keescook> (raw)
In-Reply-To: <YhihqzqPW7qbYnB9@orome>
On Fri, Feb 25, 2022 at 10:30:19AM +0100, Thierry Reding wrote:
> On Thu, Feb 24, 2022 at 07:56:08PM -0800, Kees Cook wrote:
> > Hi,
> >
> > I'm sending these again, as they still need fixing. They have been
> > rebased due to the drm_dp_helper code being moved into a subdirectory.
>
> Yeah, I noticed the other day that this had been partially reverted by
> the DP code move. I've applied this now, though it didn't apply cleanly,
> so I'll do a couple of test builds to make sure my resolution is correct
> and will push this out later on.
Awesome; thank you!
Yeah, I had based on drm/drm-next rather than drm-misc/drm-misc-next. I
wasn't sure which tree I needed to base on after the files moved.
FWIW, the resulting patches look good to me. Thanks for fixing them up!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2022-02-27 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 3:56 [PATCH v3 0/2] drm/dp: Fix out-of-bounds reads Kees Cook
2022-02-25 3:56 ` Kees Cook
2022-02-25 3:56 ` [PATCH v3 1/2] drm/dp: Fix off-by-one in register cache size Kees Cook
2022-02-25 3:56 ` Kees Cook
2022-02-25 3:56 ` [PATCH v3 2/2] drm/dp: Fix OOB read when handling Post Cursor2 register Kees Cook
2022-02-25 3:56 ` Kees Cook
2022-02-25 9:30 ` [PATCH v3 0/2] drm/dp: Fix out-of-bounds reads Thierry Reding
2022-02-25 9:30 ` Thierry Reding
2022-02-27 18:55 ` Kees Cook [this message]
2022-02-27 18:55 ` Kees Cook
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=202202271053.91D3CE109@keescook \
--to=keescook@chromium.org \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=jani.nikula@intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.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 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.