netdev - [RFC] 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: <1440367577-15786-1-git-send-email-christophe-h.ricard@st.com>
Date:	Mon, 24 Aug 2015 00:06:16 +0200
From:	Christophe Ricard <christophe.ricard@...il.com>
To:	pablo@...filter.org, jbenc@...hat.com, sameo@...ux.intel.com
Cc:	netdev@...r.kernel.org, davem@...emloft.net,
	Christophe Ricard <christophe-h.ricard@...com>
Subject: [RFC] netlink_ack: send a capped message in case of error

Hi,

I have found with netlink we can miss a ack message when exchanging large buffers.
I came across this "bug ?" when doing some tests on the NFC subsytem by trying to
send extended APDU to a secure element (up to 65K) or when sending specific device
firmware data (up to 8K) (NFC_ATTR_SE_APDU & NFC_ATTR_VENDOR_DATA).

After some search on the web, i found this topic was already threated by Jiri Benc in November 2013: 
- http://patchwork.ozlabs.org/patch/290976/
- http://www.spinics.net/lists/netdev/msg256938.html

I haven't found any update or any fix in recent kernel.

I liked the netlink message cap approach.

Do you have any update ?
Do you think a netlink message cap in netlink_ack in case of an error is an acceptable approach ?

Best Regards
Christophe

Christophe Ricard (1):
  netlink: netlink_ack send a capped message in case of error

 net/netlink/af_netlink.c | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 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