From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Justin Mattock <justinmattock@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: evdev.c(EVIOCGBIT): Suspicious buffer size 511,
Date: Wed, 20 Aug 2008 09:31:57 -0400 [thread overview]
Message-ID: <20080820092806.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080820000040.55015b48.akpm@linux-foundation.org>
On Wed, Aug 20, 2008 at 12:00:40AM -0700, Andrew Morton wrote:
> On Sun, 17 Aug 2008 23:10:54 -0700 "Justin Mattock" <justinmattock@gmail.com> wrote:
>
> > I'm noticing:
> > evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64
> > bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
> > with rc-3 not with rc2.
> > Did the patch to synaptics, seems
> > my xorg is not reading /usr/X11R6/lib/modules/input/synaptics_drv.o
> > only /usr/lib/xorg/modules/input/synaptics_drv.so
> > is there any easy fix, or do I have to recompile xorg?
> > regards;
> >
>
> (cc's added)
>
You can just copy the updated file manually into
/usr/lib/xorg/modules/input/.
I tried rebuilding synaptics from here:
git://anongit.freedesktop.org/git/xorg/driver/xf86-input-synaptics
but unfortunately it fails with some automake crap that I don't have
time to trace through at the moment.
--
Dmitry
next prev parent reply other threads:[~2008-08-20 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd18b0c30808172310u7cf7836ai15e19485908ae0ce@mail.gmail.com>
2008-08-20 7:00 ` evdev.c(EVIOCGBIT): Suspicious buffer size 511, Andrew Morton
2008-08-20 13:31 ` Dmitry Torokhov [this message]
2008-08-20 16:31 ` Justin Mattock
2008-08-21 22:47 ` Justin Mattock
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=20080820092806.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=justinmattock@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).