linux-kernel - Re: Improving read/write/close system call reliability when used with pthreads

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

Message-ID: <20070812195525.20dbb6fc@the-village.bc.nu>
Date:	Sun, 12 Aug 2007 19:55:25 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Fredrik Noring <noring@...rew.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Improving read/write/close system call reliability when used
 with pthreads

> POSIX appears to leave it "implementation-defined" provided I  
> interpret this correctly, of course. So wouldn't it be great to make  
> one of the current results a reliable feature?

Given that 99.99% of programs don't appear to care and you materially
slow down a critical path for every read and write I'm skeptical. 

Teaching the pipe code specifically to behave more nicely in this case
might be worthwhile (and as it happens with sockets in the same case you
can use shutdown() before close to get your preferred behaviour)

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/