From: Stefan Wahren <info@lategoodbye.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org
Subject: Re: serial/mxs-auart: Unable to get interrupt counter from user space
Date: Sun, 24 Jun 2012 11:14:49 +0200 [thread overview]
Message-ID: <4FE6DA89.50503@lategoodbye.de> (raw)
In-Reply-To: <20120624022547.GA7307@kroah.com>
Hi,
Am 24.06.2012 04:25, schrieb Greg KH:
> On Sat, Jun 23, 2012 at 09:19:40PM +0200, Stefan Wahren wrote:
>> Hello,
>>
>> i'm using Linux 2.6.35 at ARM and i experience the following issue
>> with the mxs-auart (App UART). If i transmit and receive data over
>> the serial port (using mxs-auart), all the interrupt counter (RX,
>> TX, frame, parity, break) accessed from user space (ioctl with
>> TIOCGICOUNT or /proc/tty/driver/auart) are zero.
>>
>> Here is the scenario to reproduce the problem:
>>
>> 1. echoing some characters to the uart device
>> 2. fetch the statistics from proc-Filesystem
>>
>> Expected results: transmit counter greater than zero
>>
>> Observed results: transmit counter is always zero
>>
>> The same szenario on the mxs-duart (Debug UART) doesn't show this problem.
>>
>> Is this a bug in mxs-auart or just not implemented?
>
> We disabled the transmit counter from being displayed a while ago for
> security reasons, perhaps that is what you are seeing?
Does this security fix affect serial_core or only mxs-auart?
Prevent this security fix from reading all counter (TX, RX, frame erros,
parity errors, breaks)?
Do you mean this security issue (
https://bugzilla.redhat.com/show_bug.cgi?id=648660 ) ?
>
> Also, you do realize just how old 2.6.35 really is, right?
Unfortunaley yes, Freescale the vendor delivers the Board Support
Package only with 2.6.35.
>
> thanks,
>
> greg k-h
>
Thanks
Stefan
next prev parent reply other threads:[~2012-06-24 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 19:19 serial/mxs-auart: Unable to get interrupt counter from user space Stefan Wahren
2012-06-24 2:25 ` Greg KH
2012-06-24 9:14 ` Stefan Wahren [this message]
2012-06-24 17:53 ` Greg KH
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=4FE6DA89.50503@lategoodbye.de \
--to=info@lategoodbye.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@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