linux-kernel - Re: Finding out socket/pipe connectivity status

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]

Date:	Sun, 12 Aug 2007 19:42:10 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: Finding out socket/pipe connectivity status

> 	write(stdout, request);
> 	/* reference point [A] */
> 	read(stdin, response);
> 
> So my idea had been to launch another thread that monitors stdin for
> 'breakage' and unmount the fs before a user can start an operation on
> myfs. So I've been trying to complete the idea to code. You say a
> broken socket raises the read flag, so:

Your connection can break at any point even mid-write so you must handle
it. You have no real choice.

You can try and spot it earlier by using select/poll and checking for
error. In which case I'd use poll() as it is a bit more clear about what
event you get

Then poll stdin and stdout. The kernel will give you back 

POLLERR - an error condition
POLLHUP - a hangup

if at the point you poll an error has already occurred. You can do this
with select and the socket error and related stuff buts its uglier

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/