linux-kernel - Re: TTY loosing data with u

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Mar 2011 19:08:02 +0200
From:	Felipe Balbi <balbi@...com>
To:	Stefan Bigler <stefan.bigler@...mile.com>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: TTY loosing data with u_serial gadget

Hi,

(please don't top-post)

On Fri, Mar 18, 2011 at 05:35:56PM +0100, Stefan Bigler wrote:
> Thanks for your quick answer. Meanwhile we ported our board to 2.6.38.
> We recognize the same problem again.
> I had also a look at the relevant fixes, a lot is done but I could not find
> the required protection of the attribute receive_room.
> 
> I added a printk in case of failure were receive_room shows more
> space that is really available in the queue and also used.
> 
> The printk is attached below and also the log.
> 
> Regards
> Stefan
> 
> 
> Log:
> flush_to_ldisc, receive_room to small count=201, receive_room=287,
> real_room=0
> flush_to_ldisc, receive_room to small count=225, receive_room=1031,
> real_room=0
> flush_to_ldisc, receive_room to small count=33, receive_room=4095,
> real_room=0


I had the same problem while I was working at Nokia developing the N900.
I even sent a patch (twice) with Alan Cox on the loop but nothing has
happened. The patch might still be floating on the archives but
essentially it would make ->receive_buf() return the amount of received
bytes (as IMHO it should be done).

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/