linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Brendan Shanks <bshanks@codeweavers.com>
Cc: linux-input@vger.kernel.org, mathieu.maret@gmail.com
Subject: Re: [PATCH] Input: evdev - Call input_flush_device() on release(), not flush()
Date: Wed, 22 Apr 2020 13:48:22 -0700	[thread overview]
Message-ID: <20200422204822.GD125362@dtor-ws> (raw)
In-Reply-To: <20200421231003.7935-1-bshanks@codeweavers.com>

On Tue, Apr 21, 2020 at 04:10:03PM -0700, Brendan Shanks wrote:
> input_flush_device() should only be called once the struct file is being
> released and no open descriptors remain, but evdev_flush() was calling
> it whenever a file descriptor was closed.
> 
> This caused uploaded force-feedback effects to be erased when a process
> did a dup()/close() on the event FD, called system(), etc.
> 
> Call input_flush_device() from evdev_release() instead.
> 
> Reported-by: Mathieu Maret <mathieu.maret@gmail.com>
> Signed-off-by: Brendan Shanks <bshanks@codeweavers.com>

Applied, thank you.

> ---
>  drivers/input/evdev.c | 18 +++---------------
>  1 file changed, 3 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index cb6e3a5f509c..3c006b265729 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -326,20 +326,6 @@ static int evdev_fasync(int fd, struct file *file, int on)
>  	return fasync_helper(fd, file, on, &client->fasync);
>  }
>  
> -static int evdev_flush(struct file *file, fl_owner_t id)
> -{
> -	struct evdev_client *client = file->private_data;
> -	struct evdev *evdev = client->evdev;
> -
> -	mutex_lock(&evdev->mutex);
> -
> -	if (evdev->exist && !client->revoked)
> -		input_flush_device(&evdev->handle, file);
> -
> -	mutex_unlock(&evdev->mutex);
> -	return 0;
> -}
> -
>  static void evdev_free(struct device *dev)
>  {
>  	struct evdev *evdev = container_of(dev, struct evdev, dev);
> @@ -453,6 +439,9 @@ static int evdev_release(struct inode *inode, struct file *file)
>  	unsigned int i;
>  
>  	mutex_lock(&evdev->mutex);
> +	if (evdev->exist && !client->revoked)
> +		input_flush_device(&evdev->handle, file);
> +
>  	evdev_ungrab(evdev, client);
>  	mutex_unlock(&evdev->mutex);
>  
> @@ -1310,7 +1299,6 @@ static const struct file_operations evdev_fops = {
>  	.compat_ioctl	= evdev_ioctl_compat,
>  #endif
>  	.fasync		= evdev_fasync,
> -	.flush		= evdev_flush,
>  	.llseek		= no_llseek,
>  };
>  
> -- 
> 2.25.3
> 

-- 
Dmitry

      reply	other threads:[~2020-04-22 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 23:10 [PATCH] Input: evdev - Call input_flush_device() on release(), not flush() Brendan Shanks
2020-04-22 20:48 ` Dmitry Torokhov [this message]

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=20200422204822.GD125362@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=bshanks@codeweavers.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mathieu.maret@gmail.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 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).