linux-kernel - Re: locks inside receive

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 for Android: free password hash cracker in your pocket

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

Message-ID: <BANLkTimm=e_fcHA-5fnT-2zQNORuJwijng@mail.gmail.com>
Date:	Tue, 17 May 2011 17:00:05 +0530
From:	Pavan Savoy <pavan_savoy@...y.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: locks inside receive_buf

<snip....>
Well apparently I can't sleep long enough, as in from inside the
tty_receive() I cannot do a tty->ops->write and wait for receive() -
since there is 1 receive_buf for 1 tty ....

Well I do have a requirement, where I must send some data from inside
the receive_buf function of a line discipline driver wait for a
certain kind of response and then proceed doing something else.

scheduling a work upon the default worker thread also doesn't seem to
be helping and the tty_receive() handler is called only after the wait
inside the work struct handler is done...

So any suggestions?
should I create a new worker thread ? or any thing simpler ?
--
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/