netdev - Re: [RFC v3] netlink: add NETLINK_CAP

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]

Date:	Thu, 27 Aug 2015 16:33:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	christophe.ricard@...il.com
Cc:	pablo@...filter.org, jbenc@...hat.com, sfeldma@...il.com,
	sameo@...ux.intel.com, netdev@...r.kernel.org,
	christophe-h.ricard@...com, stable@...r.kernel.org
Subject: Re: [RFC v3] netlink: add NETLINK_CAP_ACK socket option

From: Christophe Ricard <christophe.ricard@...il.com>
Date: Thu, 27 Aug 2015 21:31:31 +0200

> Since commit c05cdb1b864f ("netlink: allow large data transfers from
> user-space"), the kernel may fail to allocate the necessary room for the
> acknowledgment message back to userspace. This patch introduces a new
> socket option that trims off the payload of the original netlink message.
> 
> The netlink message header is still included, so the user can guess from
> the sequence number what is the message that has triggered the
> acknowledgment.
> 
> Cc: stable@...r.kernel.org

Please do not CC: stable for networking changes, that is not how we handle
-stable submissions.

Instead, please just explicitly ask me to queue it up for -stable when
you make a bonafide non-RFC submission of a change.

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