Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp377994ybi; Wed, 19 Jun 2019 00:49:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqzdbPe11uI39wzqQZzIVwGbNLyYDOxKawHoQEqAosx2342Zmv+EyM4YQkWbs8aJmydnAiDS X-Received: by 2002:a17:90a:a410:: with SMTP id y16mr9835317pjp.62.1560930569164; Wed, 19 Jun 2019 00:49:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560930569; cv=none; d=google.com; s=arc-20160816; b=IiXhP01DMb/RdxOEK2R9J8dMTDxXX/anxRWSBFMaS8On4jMRuPv8Uy3IlbGdUG6n5C LRZ1HlvMVSCZMp6msnEIVpwFnHM6eI0+AB8CepKLbBm6oeRECiMAHRRN/f4EER5cVB1e TLgvOIXQnTm29h/t7aXuGbeyocuJOelf9xPN9c73Bw5NBC+H56X/0UlW1la0WqLOul1v O/+7XkGFMkbQnLFJMW9P5llTGdmR72lCVhWuvaRaUnefgVQQFmLKdBKXfdhfBWFWDFOv T9RqVpBFXYRsMmjikoJXK6DiNYz4az0usd9WB1kXxckBOHEHY3qN/CMhkvD/EILsw+iu wAdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:mail-followup-to:message-id:subject:cc:to:from:date :dkim-signature; bh=9yRPqLsy9SzgWIOIK5gO9H41NqMgtH7z8Lf0epnTSe8=; b=sCI4oE4LfTNpbS5/zYkcHUsGhP3QeP9PK3eRTIrrHeJeS0jF6Sag1KCFMdTqUmxO9a 0QofsESFbmmHhAslSY4rDimPf4MBS18Gizxcet4rMFY5nyvoMWSD1ahi7rP/HohFXEIO ZBGRbi69uRTl+B139wj3MjA4HpZeubU/XOWS+zMwVQ8IjmSH+jIWkp9oCdFIuhh6gIQX IIrw9U0exwxa/7Xu9zUwKnt406zrtggNyvCEZmaCYohMhSJh1oEonZ5ME7WX5QNkvBSV TZmJKEc21y2zeEPQf9g+njhwGKck5BhXTQUMPlZ8WXD2RG4DByLRIgwt7N2AsbOx3phu RwiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=jWHFk6Xq; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l67si16155736plb.370.2019.06.19.00.49.13; Wed, 19 Jun 2019 00:49:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=jWHFk6Xq; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731232AbfFSHtD (ORCPT + 99 others); Wed, 19 Jun 2019 03:49:03 -0400 Received: from mail-ed1-f65.google.com ([209.85.208.65]:33241 "EHLO mail-ed1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725980AbfFSHtC (ORCPT ); Wed, 19 Jun 2019 03:49:02 -0400 Received: by mail-ed1-f65.google.com with SMTP id i11so25796470edq.0 for ; Wed, 19 Jun 2019 00:49:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=9yRPqLsy9SzgWIOIK5gO9H41NqMgtH7z8Lf0epnTSe8=; b=jWHFk6XqsoYXocFpSE0gn/gHZJ/0TrxElZKm42Ipe0ZdlxBiXBmyo9fX4/WGgeDDO3 8AYZ0F+ufO1zlDHVBmH9vwwSvpWZI8HJCpZq3I4Sx2ZL54GWsm81cgHwZAzplxF8c3Me oI3KswqH2dD74mtl53UCCeWZ6zPk1dUxbOPMc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=9yRPqLsy9SzgWIOIK5gO9H41NqMgtH7z8Lf0epnTSe8=; b=XcQyYj4AT9CzjAaaBQ3hz778vsC3sFThe5DTwcJDTRYgXqspeFYrPbdcGzuZ11UDkt NRqhb2GEU/tUVYNMH/0EE+Qr9fIroy/Y+LJ0jb7jKA9zPbgNQOB6NntG9Vtr9/KlJuKB FATLYuFEmUKLIka11dbVakg0bCEAWG6x8lyiGliIkFEDSX7fI6aF6qjdAtYPH958fsDs 2hGr2+eqEClHcUK49kxQaLlG8sQYN2yKnIBVAV4V1a5a9lqyilvT0glfxhnqvCqeULAx hnrQiZcC8TcoobfHJquyUbedrN3tthdMJZCOANRmqPeDYOium0dBxMjVwAWWMmM/ilrR w3jw== X-Gm-Message-State: APjAAAXmJZXe+nqDQIKORzoFVwTfTas5QtCExELVX858Vh7Uns19frfW o4Forgr/cdu48FObu83RJNB+IQ== X-Received: by 2002:a50:883b:: with SMTP id b56mr36295341edb.178.1560930540342; Wed, 19 Jun 2019 00:49:00 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:569e:0:3106:d637:d723:e855]) by smtp.gmail.com with ESMTPSA id x4sm5546030eda.22.2019.06.19.00.48.59 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 19 Jun 2019 00:48:59 -0700 (PDT) Date: Wed, 19 Jun 2019 09:48:56 +0200 From: Daniel Vetter To: Rodrigo Siqueira Cc: Maarten Lankhorst , Maxime Ripard , Sean Paul , David Airlie , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, intel-gfx@lists.freedesktop.org Subject: Re: [PATCH V4] drm/drm_vblank: Change EINVAL by the correct errno Message-ID: <20190619074856.GJ12905@phenom.ffwll.local> Mail-Followup-To: Rodrigo Siqueira , Maarten Lankhorst , Maxime Ripard , Sean Paul , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, intel-gfx@lists.freedesktop.org References: <20190619020750.swzerehjbvx6sbk2@smtp.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190619020750.swzerehjbvx6sbk2@smtp.gmail.com> X-Operating-System: Linux phenom 4.19.0-5-amd64 User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 18, 2019 at 11:07:50PM -0300, Rodrigo Siqueira wrote: > For historical reason, the function drm_wait_vblank_ioctl always return > -EINVAL if something gets wrong. This scenario limits the flexibility > for the userspace make detailed verification of the problem and take > some action. In particular, the validation of “if (!dev->irq_enabled)” > in the drm_wait_vblank_ioctl is responsible for checking if the driver > support vblank or not. If the driver does not support VBlank, the > function drm_wait_vblank_ioctl returns EINVAL which does not represent > the real issue; this patch changes this behavior by return EOPNOTSUPP. > Additionally, some operations are unsupported by this function, and > returns EINVAL; this patch also changes the return value to EOPNOTSUPP > in this case. Lastly, the function drm_wait_vblank_ioctl is invoked by > libdrm, which is used by many compositors; because of this, it is > important to check if this change breaks any compositor. In this sense, > the following projects were examined: > > * Drm-hwcomposer > * Kwin > * Sway > * Wlroots > * Wayland-core > * Weston > * Xorg (67 different drivers) > > For each repository the verification happened in three steps: > > * Update the main branch > * Look for any occurrence "drmWaitVBlank" with the command: > git grep -n "drmWaitVBlank" > * Look in the git history of the project with the command: > git log -SdrmWaitVBlank > > Finally, none of the above projects validate the use of EINVAL which > make safe, at least for these projects, to change the return values. > > Change since V3: > - Return EINVAL for _DRM_VBLANK_SIGNAL (Daniel) > > Change since V2: > Daniel Vetter and Chris Wilson > - Replace ENOTTY by EOPNOTSUPP > - Return EINVAL if the parameters are wrong > Reviewed-by: Daniel Vetter Apologies for the confusion on the last time around. btw if someone tells you "r-b (or a-b) with these changes", then just apply the r-b/a-b tag next time around. Otherwise people will re-review the same thing over and over again. -Daniel > Signed-off-by: Rodrigo Siqueira > --- > drivers/gpu/drm/drm_vblank.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/drm_vblank.c b/drivers/gpu/drm/drm_vblank.c > index 603ab105125d..bed233361614 100644 > --- a/drivers/gpu/drm/drm_vblank.c > +++ b/drivers/gpu/drm/drm_vblank.c > @@ -1582,7 +1582,7 @@ int drm_wait_vblank_ioctl(struct drm_device *dev, void *data, > unsigned int flags, pipe, high_pipe; > > if (!dev->irq_enabled) > - return -EINVAL; > + return -EOPNOTSUPP; > > if (vblwait->request.type & _DRM_VBLANK_SIGNAL) > return -EINVAL; > -- > 2.21.0 -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch