linux-kernel - Re: Hardware initialization in line discipline

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]

Message-ID: <20091015223137.6b9fb55a@lxorguk.ukuu.org.uk>
Date:	Thu, 15 Oct 2009 22:31:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Peter Stuge <peter@...ge.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hardware initialization in line discipline - ldisc_open() ?

> Since the packet format is the same it would be easy to reuse the
> normal ldisc receive path for the handshake, however the ldisc would
> not see the response until after ldisc_open() has succeeded.

Indeed.

> Can you suggest a solution to this problem? Ideally one that can be
> contained in the ldisc.

Similar problem with the GSM mux I've been working on. I've gone for
making the ldisc attach always work and then kicking things off via an
ioctl which sets the desired mode/parameters/encoding.
--
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/