netdev - Re: [PATCH 2.6.27.7-9-pae #7 SMP 1/1] networking tcp: Writing tcp socket be atomic

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: <20100203.181931.39810642.davem@davemloft.net>
Date:	Wed, 03 Feb 2010 18:19:31 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	johny@...mco.com.cn
Cc:	kuznet@....inr.ac.ru, netdev@...r.kernel.org, jmorris@...ei.org,
	kaber@...eworks.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.27.7-9-pae #7 SMP 1/1] networking tcp: Writing tcp
 socket be atomic

From: "John Ye" <johny@...mco.com.cn>
Date: Thu, 4 Feb 2010 10:03:44 +0800

> The option TCP_ATOMIC is not a must.  We can make atomic be default
> if the data size is less than a fixed size, just the same as pipe.
> For example, if the data size is less than 512, we don't split the
> data so it goes atomically.

This completely ignores the core issue.

And that is, for the second time, that the application is where such
atomicity guarentees should be implemented.

And because of that any implementation of your kernel changes are
inappropriate, TCP_ATOMIC socket option or not.
--
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