linux-kernel - Re: [PATCH] IPROUTE: correct nla nested message generated by netem_parse

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: <20080828101840.GZ20815@postel.suug.ch>
Date:	Thu, 28 Aug 2008 12:18:40 +0200
From:	Thomas Graf <tgraf@...g.ch>
To:	David Miller <davem@...emloft.net>
Cc:	alexander.duyck@...il.com, shemminger@...tta.com,
	jeffrey.t.kirsher@...el.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	alexander.h.duyck@...el.com
Subject: Re: [PATCH] IPROUTE: correct nla nested message generated by netem_parse_opt

* David Miller <davem@...emloft.net> 2008-08-27 23:47
> It doesn't matter what "correct" compat nested attribute parsing
> is or is not.  The fact is that RR and PRIO were using a certain
> format, consistently, prior to commit #6.  This is what was
> codified in userspace in the iproute2 sources and worked
> correctly until #6.

So we remove nla_parsed_nested_compat() just to add it again under
a different name since netem is still going to use that piece of
code. That certainly makes sense. Fixing prio and rr in stable is
a one liner.
--
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/