netdev - [RFC v2] netlink_ack: send a capped message in case of error

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

Message-Id: <1440531809-26963-1-git-send-email-christophe-h.ricard@st.com>
Date:	Tue, 25 Aug 2015 21:43:28 +0200
From:	Christophe Ricard <christophe.ricard@...il.com>
To:	pablo@...filter.org, jbenc@...hat.com, sfeldma@...il.com,
	sameo@...ux.intel.com, davem@...emloft.net
Cc:	netdev@...r.kernel.org,
	Christophe Ricard <christophe-h.ricard@...com>
Subject: [RFC v2] netlink_ack: send a capped message in case of error

Hi,

Thanks to my first RFC proposal to cap a netlink message in case of an error, i have
rebased my work on Pablo Neira Ayuso.
After some few trials, it appears to me in_skb->sk is not the correct socket to deal with.

Here comes a reworked and tested version based on Pablo's one.

Also i believe it could be good to make it reach stable as it is somehow a bug fix.

What do you think ?

Best Regards
Christophe

Christophe Ricard (1):
  netlink: add NETLINK_CAP_ACK socket option

 include/uapi/linux/netlink.h |  1 +
 net/netlink/af_netlink.c     | 49 ++++++++++++++++++++++++++++++++------------
 2 files changed, 37 insertions(+), 13 deletions(-)

-- 
2.1.4

--
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