From: Peter Hurley <peter@hurleysoftware.com>
To: Jiri Slaby <jslaby@suse.cz>, Denis Du <dudenis2000@yahoo.ca>,
gregkh@linuxfoundation.org, jmmahler@gmail.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] TTY: Fix the missing lock for the TTY ldisc buffer
Date: Wed, 10 Dec 2014 14:33:10 -0500 [thread overview]
Message-ID: <54889FF6.2000508@hurleysoftware.com> (raw)
In-Reply-To: <548895D9.6090402@suse.cz>
On 12/10/2014 01:50 PM, Jiri Slaby wrote:
> On 12/10/2014, 07:38 PM, Denis Du wrote:
>>
>> Hi, Guys:
>
> Hi, are you sending this using some robot? I think I have seen like ten
> copies of this patch already.
>
>> It was found that the 3.12 kernel tty layer will lose or corrupt data
>> when have a full-duplex communication, especially in high baud rate, for
>> example 230k for my OMAP5 uart. Eventually I found there is lock missing
>> between copy data to ldisc layer buffer and copy data from the same
>> buffer to user space. I believe this issue existed since 3.8
>> kernel(since this kernel , it start to remove most of the spin-locks)
>> and I didn't find any fix even through 3.17 kernel. This patch was
>> tested to be works great with no any data loss again on 3.12 kernel.
>>
>> This patch was built for the latest kernel, but I cannot test it.
>> Somebody may give a test.
>>
>> I did try to use the existed lock atomic_read_lock, but it doesn’t work.
>
> Anyway, adding Peter Hurley to CC who was working on eliminating locks
> from this code lately. More precisely since 3.12 we have no locks there,
> which would explain why are you seeing it starting 3.12.
Yeah, sorry. A new version of gcc for ARM exposed the lack of barriers for
the head pointer in raw mode. I got tied up on something else, but this
is my #1 priority now.
I hope to have something testable in the next day or two.
Sorry for the delay.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-12-10 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 18:38 [PATCH] TTY: Fix the missing lock for the TTY ldisc buffer Denis Du
2014-12-10 18:50 ` Jiri Slaby
2014-12-10 18:57 ` Denis Du
2014-12-10 19:33 ` Peter Hurley [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 18:32 Denis Du
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=54889FF6.2000508@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=dudenis2000@yahoo.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jmmahler@gmail.com \
--cc=jslaby@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.