dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/fb-helper: Only reject FB changes if FB_MISC_USER_EVENT is set
Date: Fri, 17 Mar 2017 12:01:33 +0200	[thread overview]
Message-ID: <20170317100133.GO31595@intel.com> (raw)
In-Reply-To: <87d59360-8419-b547-7b6b-32afedcf1330@daenzer.net>

On Fri, Mar 17, 2017 at 06:01:41PM +0900, Michel Dänzer wrote:
> On 16/03/17 07:09 PM, Ville Syrjälä wrote:
> > On Thu, Mar 16, 2017 at 06:55:53PM +0900, Michel Dänzer wrote:
> >> From: Michel Dänzer <michel.daenzer@amd.com>
> >>
> >> Otherwise this can also prevent modesets e.g. for switching VTs.
> >>
> >> FB_MISC_USER_EVENT is set when the request originates from userspace,
> >> which is what we're interested in here according to the DRM_DEBUG
> >> output.
> > 
> > So why is the kernel allowed to violate this?
> > 
> > The checks look somewhat bogus to me anyway. The 'virtual size == fb size'
> > check makes some kind of sense. Although I don't see why the virtual
> > resolution couldn't be smaller than the fb size. But requiring that the
> > visible resolutionn matches the fb size as well definitely seems wrong.
> 
> Agreed on all counts. So, I think what's needed is almost a revert of
> 865afb11949e, except for the bits_per_pixel comparison, since we really
> can't change that. See diff below.

So one semi-crazy idea I had was:
12:18 < vsyrjala> daniels: hmm. given that the fb_helper doesn't
 implement a modeset in set_par, i guess what we really
 should do is look at the currently active crtcs and see if the mode on
 one of them more or less matches what the user is asking for

I tried to trip this current check by booting with a big screen and
later switching to a small screen. For some reason that worked out
just fine, so I'm not even sure what kind of values we stuff into
xres & co.

> 
> Does that make sense? Stefan, would this break any test case you wrote
> your patch for?
> 
> 
> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> index f6d4d9700734..f4f70ce24fcc 100644
> --- a/drivers/gpu/drm/drm_fb_helper.c
> +++ b/drivers/gpu/drm/drm_fb_helper.c
> @@ -1260,8 +1260,8 @@ int drm_fb_helper_check_var(struct fb_var_screeninfo *var,
>          * to KMS, hence fail if different settings are requested.
>          */
>         if (var->bits_per_pixel != fb->format->cpp[0] * 8 ||
> -           var->xres != fb->width || var->yres != fb->height ||
> -           var->xres_virtual != fb->width || var->yres_virtual != fb->height) {
> +           var->xres > fb->width || var->yres > fb->height ||
> +           var->xres_virtual > fb->width || var->yres_virtual > fb->height) {
>                 DRM_DEBUG("fb userspace requested width/height/bpp different than current fb "
>                           "request %dx%d-%d (virtual %dx%d) > %dx%d-%d\n",
>                           var->xres, var->yres, var->bits_per_pixel,
> 
> 
> 
> >> Bugzilla: https://bugs.freedesktop.org/99841
> >> Fixes: 865afb11949e ("drm/fb-helper: reject any changes to the fbdev")
> >> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
> >> ---
> >>
> >> I'm not entirely sure why the values can not match for a VT switch. If
> >> anybody thinks this just papers over the real issue, please speak up.
> >>
> >>  drivers/gpu/drm/drm_fb_helper.c | 7 ++++---
> >>  1 file changed, 4 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> >> index f6d4d9700734..9663f3b8f287 100644
> >> --- a/drivers/gpu/drm/drm_fb_helper.c
> >> +++ b/drivers/gpu/drm/drm_fb_helper.c
> >> @@ -1259,9 +1259,10 @@ int drm_fb_helper_check_var(struct fb_var_screeninfo *var,
> >>  	 * Changes struct fb_var_screeninfo are currently not pushed back
> >>  	 * to KMS, hence fail if different settings are requested.
> >>  	 */
> >> -	if (var->bits_per_pixel != fb->format->cpp[0] * 8 ||
> >> -	    var->xres != fb->width || var->yres != fb->height ||
> >> -	    var->xres_virtual != fb->width || var->yres_virtual != fb->height) {
> >> +	if ((info->flags & FBINFO_MISC_USEREVENT) &&
> >> +	    (var->bits_per_pixel != fb->format->cpp[0] * 8 ||
> >> +	     var->xres != fb->width || var->yres != fb->height ||
> >> +	     var->xres_virtual != fb->width || var->yres_virtual != fb->height)) {
> >>  		DRM_DEBUG("fb userspace requested width/height/bpp different than current fb "
> >>  			  "request %dx%d-%d (virtual %dx%d) > %dx%d-%d\n",
> >>  			  var->xres, var->yres, var->bits_per_pixel,
> >> -- 
> >> 2.11.0
> >>
> >> _______________________________________________
> >> dri-devel mailing list
> >> dri-devel@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> > 
> 
> 
> -- 
> Earthling Michel Dänzer               |               http://www.amd.com
> Libre software enthusiast             |             Mesa and X developer

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-03-17 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16  9:55 [PATCH] drm/fb-helper: Only reject FB changes if FB_MISC_USER_EVENT is set Michel Dänzer
2017-03-16 10:09 ` Ville Syrjälä
2017-03-17  9:01   ` Michel Dänzer
2017-03-17 10:01     ` Ville Syrjälä [this message]
2017-03-17 10:19       ` Michel Dänzer
2017-03-17 11:13         ` Ville Syrjälä
2017-03-21  3:24           ` Michel Dänzer
2017-03-16 10:09 ` Daniel Stone
2017-03-17  8:54   ` Michel Dänzer
2017-03-23  8:53 ` [PATCH] drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again Michel Dänzer
2017-03-23 12:01   ` Daniel Stone
2017-03-23 13:59     ` Daniel Vetter
2017-03-24  0:42   ` Stefan Agner

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=20170317100133.GO31595@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@daenzer.net \
    /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).