From: Lyude Paul <cpaul@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/fb_helper: Fix references to dev->mode_config.num_connector
Date: Thu, 05 May 2016 11:27:33 -0400 [thread overview]
Message-ID: <1462462053.30874.3.camel@redhat.com> (raw)
In-Reply-To: <20160504171135.GF1286@phenom.ffwll.local>
I would Cc it to stable just in case tbh. I picked up on this one since KASAN
was picking up on some of the memcpy() calls around here going out of bounds. I
can include some of the backtraces from that if needed.
On Wed, 2016-05-04 at 19:11 +0200, Daniel Vetter wrote:
> On Wed, May 04, 2016 at 11:28:52AM -0400, Lyude wrote:
> >
> > During boot, MST hotplugs are generally expected (even if no physical
> > hotplugging occurs) and result in DRM's connector topology changing.
> > This means that using num_connector from the current mode configuration
> > can lead to the number of connectors changing under us. This can lead to
> > some nasty scenarios in fbcon:
> >
> > - We allocate an array to the size of dev->mode_config.num_connectors.
> > - MST hotplug occurs, dev->mode_config.num_connectors gets incremented.
> > - We try to loop through each element in the array using the new value
> > of dev->mode_config.num_connectors, and end up going out of bounds
> > since dev->mode_config.num_connectors is now larger then the array we
> > allocated.
> >
> > fb_helper->connector_count however, will always remain consistent while
> > we do a modeset in fb_helper.
> >
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Lyude <cpaul@redhat.com>
> Ok, this one looks like it's indeed in the same critical section (within
> drm_setup_outputs) as where we allocate the fb helper connector array. So
> I think this one here is not needed to fix a bug?
>
> Still makes sense as a patch, but not with cc: stable I think.
> -Daniel
>
> >
> > ---
> > drivers/gpu/drm/drm_fb_helper.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_fb_helper.c
> > b/drivers/gpu/drm/drm_fb_helper.c
> > index 855108e..15204c0 100644
> > --- a/drivers/gpu/drm/drm_fb_helper.c
> > +++ b/drivers/gpu/drm/drm_fb_helper.c
> > @@ -1914,7 +1914,7 @@ static int drm_pick_crtcs(struct drm_fb_helper
> > *fb_helper,
> > if (modes[n] == NULL)
> > return best_score;
> >
> > - crtcs = kzalloc(dev->mode_config.num_connector *
> > + crtcs = kzalloc(fb_helper->connector_count *
> > sizeof(struct drm_fb_helper_crtc *), GFP_KERNEL);
> > if (!crtcs)
> > return best_score;
> > @@ -1960,7 +1960,7 @@ static int drm_pick_crtcs(struct drm_fb_helper
> > *fb_helper,
> > if (score > best_score) {
> > best_score = score;
> > memcpy(best_crtcs, crtcs,
> > - dev->mode_config.num_connector *
> > + fb_helper->connector_count *
> > sizeof(struct drm_fb_helper_crtc *));
> > }
> > }
> > --
> > 2.5.5
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Cheers,
Lyude
next prev parent reply other threads:[~2016-05-05 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 15:28 [PATCH 1/3] drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config() Lyude
2016-05-04 15:28 ` Lyude
2016-05-04 15:28 ` [PATCH 2/3] drm/fb_helper: Fix references to dev->mode_config.num_connector Lyude
2016-05-04 15:28 ` Lyude
2016-05-04 17:11 ` Daniel Vetter
2016-05-04 17:11 ` Daniel Vetter
2016-05-05 15:27 ` Lyude Paul [this message]
2016-05-04 15:28 ` [PATCH 3/3] drm/fb_helper: Fix a few typos Lyude
2016-05-04 15:28 ` Lyude
2016-05-04 16:11 ` Daniel Vetter
2016-05-04 16:11 ` [Intel-gfx] " Daniel Vetter
2016-05-04 16:17 ` [PATCH 1/3] drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config() Daniel Vetter
2016-05-04 16:17 ` Daniel Vetter
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=1462462053.30874.3.camel@redhat.com \
--to=cpaul@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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.