netdev - Re: [PATCH] drop_monitor: Update netlink protocol to include netlink attribute header in alert message

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: <20090427.031746.166472203.davem@davemloft.net>
Date:	Mon, 27 Apr 2009 03:17:46 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	nhorman@...driver.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] drop_monitor: Update netlink protocol to include
 netlink attribute header in alert message

From: Neil Horman <nhorman@...driver.com>
Date: Thu, 23 Apr 2009 16:05:48 -0400

> When I initially implemented this protocol, I disregarded the use of netlink
> attribute headers, thinking for my purposes they weren't needed.  I've come to
> find out that, as I'm starting to work with sending down messages with
> associated data (like config messages), the kernel code spits out warnings about
> trailing data in a netlink skb that doesn't have an associated header on it.  As
> such, I'm going to start including attribute headers in my netlink transaction,
> and so for completeness, I should likely include them on messages bound from the
> kernel to user space.  This patch adds that header to the kernel, and bumps the
> protocol version accordingly
> 
> Signed-off-by: Neil Horman <nhorman@...driver.com>

Applied to net-next-2.6, thanks Neil.
--
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