| 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
| ||
|
Date: Wed, 20 Aug 2008 15:20:09 -0700 From: "Duyck, Alexander H" <alexander.h.duyck@...el.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org> CC: "shemminger@...l.org" <shemminger@...l.org>, "tgraf@...g.ch" <tgraf@...g.ch>, "Brandeburg, Jesse" <jesse.brandeburg@...el.com>, "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com> Subject: Question on netlink nested attributes I have a regression that was found in 2.6.26 in which the multiqueue option for the prio qdisc quit working after the commit referenced at http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.26.y.git;a=commit;h=b9a2f2e450b0f770bb4347ae8d48eb2dea701e24 The issue appears to be that the prio qdisc and the netem qdisc have two different ways that they are nesting the attributes they are passing to the qdisc layer but both use nla_parse_nested_compat. The prio qdisc is laying out the message something like: hdr0(data+hdr1(hdr2(data)+hdr3(data))) The netem qdisc is laying out the message something like: hdr0(data+hdr2(data)+hdr3(data)) There is essentially an option header missing in the netem version of the nested netlink attributes message. The patch that went in seems to make things work without warnings for the netem approach but broke things for the prio approach. The question is which format is correct. Just need to know so I can go about getting them both working the same way. Thanks, Alex -- 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
Powered by blists - more mailing lists