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

Message-ID: <20110317235532.44c0e202@lxorguk.ukuu.org.uk>
Date:	Thu, 17 Mar 2011 23:55:32 +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.

On Thu, 17 Mar 2011 18:20:22 -0400
Sergey Lapin <slapin@...fans.org> wrote:

> Normally, when LAPB is transport layer for X.25 protocol,
> internal mechanics of X.25 knows wheather data were actually
> received by peer. But for non-X.25 protocols which use LAPB
> as data reliability layer, it is important to have some way
> to know what was actually sent, so we add transmit indication.

Looks sensible but your patch doesn't add a user for it so what is it
needed for ?
--
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/