linux-kernel - Re: [PATCH] Allow LAPB users know which data were actually sent.

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] [day] [month] [year] [list]

Message-ID: <20110318113433.39794ca5@lxorguk.ukuu.org.uk>
Date:	Fri, 18 Mar 2011 11:34:33 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Sergey Lapin <slapin@...fans.org>
Cc:	linux-x25@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Allow LAPB users know which data were actually sent.

> > Looks sensible but your patch doesn't add a user for it so what is it
> > needed for ?
> 
> I implement accessor for special equipment (acessing fiscal information)
> which uses custom protocol over LAPB. As it is being implemented,
> I actually wanted to know if this approach for using LAPB is good enough
> for mainline submission, as I want to have kernel part to be in mainline.
> I think I will have the rest of patches ready within two weeks.

It seems sensible as an implementation to me so I would carry on using
that model and then submit it with all the other bits when you are ready.
--
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/