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: <20070812161337.3828381c@the-village.bc.nu>
Date:	Sun, 12 Aug 2007 16:13:37 +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

> For (1), a simple scenario has two threads: a reader and a watchdog.  
> The reader thread is stuck in a blocking read of an unreliable pipe.  
> The watchdog thread is designed to cancel the blocking read using  
> close on the reader's fd.

The reader still has the fd open so the fd is not yet closed. This seems
completely sane to me. Closing the *writer* fd would create an EOF which
is the proper response.

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/