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]

Date:	Sun, 18 Oct 2009 18:27:37 +0200
From:	Peter Stuge <peter@...ge.se>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hardware initialization in line discipline - ldisc_open() ?

Alan Cox wrote:
> > > 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.
> > 
> > I'll do the same. Did you add a new ioctl for this, or use an
> > existing one?
> 
> I added a private one - given I needed to pass the adaption layer code,
> gsm mux level and whether we were initiator or not it didn't really fit
> anything generic in the tty layer.

I was trying to reuse an existing ioctl, partly because I'm not sure
how to add a one and partly because fewer are better, but
TIOCSERCONFIG which seemed fitting does not appear to be passed on to
my ldisc. :\

Should I make a new one (what does private mean here btw?) and how do
I do it exactly? Is patching Documentation/ioctl/ioctl-number.txt and
asm/ioctls.h all? The "addressing" in ioctl-number seems a little
chaotic, do I just pick anything that is available?

//Peter
--
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/