linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
	David Herrmann <dh.herrmann@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: evdev - get rid of old workaround for EVIOCGBIT
Date: Thu, 24 Apr 2014 15:37:38 +1000	[thread overview]
Message-ID: <20140424053738.GA1839@yabbi.redhat.com> (raw)
In-Reply-To: <20140424052719.GA29764@core.coreip.homeip.net>

On Wed, Apr 23, 2014 at 10:27:20PM -0700, Dmitry Torokhov wrote:
> We put this workaround in 2008 and the offending userspace has been fixed
> up long time ago; the link in the message is no longer valid either, so it
> is time to retire it.
> 
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

works for me, Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

Cheers,
   Peter

> ---
>  drivers/input/evdev.c | 18 ------------------
>  1 file changed, 18 deletions(-)
> 
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index ce953d8..fd325ec 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -629,12 +629,10 @@ static int str_to_user(const char *str, unsigned int maxlen, void __user *p)
>  	return copy_to_user(p, str, len) ? -EFAULT : len;
>  }
>  
> -#define OLD_KEY_MAX	0x1ff
>  static int handle_eviocgbit(struct input_dev *dev,
>  			    unsigned int type, unsigned int size,
>  			    void __user *p, int compat_mode)
>  {
> -	static unsigned long keymax_warn_time;
>  	unsigned long *bits;
>  	int len;
>  
> @@ -652,24 +650,8 @@ static int handle_eviocgbit(struct input_dev *dev,
>  	default: return -EINVAL;
>  	}
>  
> -	/*
> -	 * Work around bugs in userspace programs that like to do
> -	 * EVIOCGBIT(EV_KEY, KEY_MAX) and not realize that 'len'
> -	 * should be in bytes, not in bits.
> -	 */
> -	if (type == EV_KEY && size == OLD_KEY_MAX) {
> -		len = OLD_KEY_MAX;
> -		if (printk_timed_ratelimit(&keymax_warn_time, 10 * 1000))
> -			pr_warning("(EVIOCGBIT): Suspicious buffer size %u, "
> -				   "limiting output to %zu bytes. See "
> -				   "http://userweb.kernel.org/~dtor/eviocgbit-bug.html\n",
> -				   OLD_KEY_MAX,
> -				   BITS_TO_LONGS(OLD_KEY_MAX) * sizeof(long));
> -	}
> -
>  	return bits_to_user(bits, len, size, p, compat_mode);
>  }
> -#undef OLD_KEY_MAX
>  
>  static int evdev_handle_get_keycode(struct input_dev *dev, void __user *p)
>  {
> -- 
> 1.9.0
> 
> 
> -- 
> Dmitry

  reply	other threads:[~2014-04-24  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  5:27 [PATCH] Input: evdev - get rid of old workaround for EVIOCGBIT Dmitry Torokhov
2014-04-24  5:37 ` Peter Hutterer [this message]
2014-04-29  8:06 ` David Herrmann

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=20140424053738.GA1839@yabbi.redhat.com \
    --to=peter.hutterer@who-t.net \
    --cc=dh.herrmann@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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 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).