netdev - Re: [PATCH] tcp: detect loss above high

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: <20111228.130736.79570418506453470.davem@davemloft.net>
Date:	Wed, 28 Dec 2011 13:07:36 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	ilpo.jarvinen@...sinki.fi
Cc:	ycheng@...gle.com, ncardwell@...gle.com, nanditad@...gle.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH] tcp: detect loss above high_seq in recovery

From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Wed, 28 Dec 2011 17:42:06 +0200 (EET)

> I don't think you can remove MIBs as they're userspace visible.

Because of how they are implemented and how applications use them,
this is actually allowed.

All the MIBs are presented first as a series of strings, then as a
series of values.

So applications parse them both to report the statistics, and this do
get coded in a way that they do not need to assume the presence or
particular ordering of these MIBS.

Therefore, such a change is safe.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html