From: Stephen Chandler Paul <cpaul@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] i8042: Add debug_kbd option
Date: Thu, 25 Jun 2015 17:31:25 -0400 [thread overview]
Message-ID: <1435267885.2972.4.camel@redhat.com> (raw)
In-Reply-To: <20150625203238.GA27620@dtor-ws>
On Thu, 2015-06-25 at 13:32 -0700, Dmitry Torokhov wrote:
> On Thu, Jun 25, 2015 at 03:25:10PM -0400, cpaul@redhat.com wrote:
> > From: Stephen Chandler Paul <cpaul@redhat.com>
> >
> > A big problem with the current i8042 debugging option is that it
> > outputs
> > data going to and from the keyboard by default. As a result, many
> > dmesg
> > logs uploaded by users will unintentionally contain sensitive
> > information
> > such as their password, as such it's probably a good idea not to
> > output
> > data coming from the keyboard unless specifically enabled by the
> > user.
> >
> > Signed-off-by: Stephen Chandler Paul <cpaul@redhat.com>
> > Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > ---
> > Documentation/kernel-parameters.txt | 7 +++++++
> > drivers/input/serio/i8042.c | 25 +++++++++++++++++++++----
> > 2 files changed, 28 insertions(+), 4 deletions(-)
> >
> > diff --git a/Documentation/kernel-parameters.txt
> > b/Documentation/kernel-parameters.txt
> > index ae44749..9e00234 100644
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -1304,6 +1304,13 @@ bytes respectively. Such letter suffixes can
> > also be entirely omitted.
> > <bus_id>,<clkrate>
> >
> > i8042.debug [HW] Toggle i8042 debug mode
> > + i8042.debug_kbd [HW] Enable printing of interrupt data
> > from the KBD port
> > + As a side effect, this option will
> > mask some of the
> > + interrupts sent back from the
> > keyboard during the
> > + initialization of the KBD port on the
> > i8042, if you
> > + need to see this, you will need to
> > enable this
> > + option.
>
> Hmm, can we maybe use the bus notifier and react to
> BUS_NOTIFY_BOUND_DRIVER/BUS_NOTIFY_UNBIND_DRIVER to decide if we want
> to
> see keyboard data stream?
Out of curiosity, are there devices that aren't keyboards that actually
make use of the KBD port? It was my understanding keyboards used the
KBD port, and everything else uses the AUX port.
Regardless, I'm looking into doing this as we speak.
Cheers,
Stephen Chandler Paul
>
> Thanks.
>
next prev parent reply other threads:[~2015-06-25 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 19:25 [PATCH] i8042: Add debug_kbd option cpaul
2015-06-25 20:00 ` Joe Perches
2015-06-25 20:32 ` Dmitry Torokhov
2015-06-25 21:31 ` Stephen Chandler Paul [this message]
2015-06-25 21:35 ` Dmitry Torokhov
2015-06-25 22:12 ` Stephen Chandler Paul
2015-06-26 19:28 ` [PATCH v2] " cpaul
2015-06-26 22:28 ` [PATCH v3] " cpaul
2015-06-26 23:05 ` Dmitry Torokhov
2015-06-26 23:21 ` Stephen Chandler Paul
2015-06-26 23:24 ` Dmitry Torokhov
2015-06-27 0:24 ` [PATCH v4] " cpaul
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=1435267885.2972.4.camel@redhat.com \
--to=cpaul@redhat.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.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