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: <B37532D9-870C-4412-8ADF-83E20F75E18A@nocrew.org>
Date:	Sun, 12 Aug 2007 21:19:39 +0200
From:	Fredrik Noring <noring@...rew.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Improving read/write/close system call reliability when used with pthreads

Alan,

Alan Cox wrote:
> 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.

I've made required_fds a struct list_head list to accommodate for  
multiple fd:s (not sure that's absolutely needed though), so a couple  
of pointers need to be updated in sys_read/write. However, if that's  
too slow, and we only care about bookkeeping a single fd which is the  
case with sys_read/write, that can be changed into a single fd  
integer assignment.

Would that be fast enough?

Fredrik

-
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/