linux-kernel - Re: New AIO API

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]

Date:	Tue, 16 Apr 2013 19:48:40 +0200
From:	Jan Kara <jack@...e.cz>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Kent Overstreet <koverstreet@...gle.com>, linux-aio@...ck.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	lsf-pc@...ts.linux-foundation.org, Zach Brown <zab@...hat.com>,
	Felipe Balbi <balbi@...com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Mark Fasheh <mfasheh@...e.com>,
	Joel Becker <jlbec@...lplan.org>, Jens Axboe <axboe@...nel.dk>,
	Asai Thambi S P <asamymuthupa@...ron.com>,
	Selvan Mani <smani@...ron.com>,
	Sam Bradshaw <sbradshaw@...ron.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Benjamin LaHaise <bcrl@...ck.org>,
	Theodore Ts'o <tytso@....edu>
Subject: Re: New AIO API

On Tue 16-04-13 10:48:35, Rusty Russell wrote:
> Andrew Morton <akpm@...ux-foundation.org> writes:
> > On Fri, 12 Apr 2013 15:28:56 -0700 Kent Overstreet <koverstreet@...gle.com> wrote:
> >> Those are the main changes (besides adding attributes, of course) that
> >> I've made so far. 
> >> 
> >>  * Get rid of the parallel syscall interface 
> >> 
> >>    AIO really shouldn't be implementing its own slightly different
> >>    syscalls; it should be a mechanism for doing syscalls asynchronously.
> >
> > Yes.  We got about a twelfth of the way there many years ago
> > (google("syslets")) but it died.  A shame.
> 
> Yeah, letting the current process keep waiting and creating a new one
> which returns is a fascinating idea, but you really need to swizzle the
> PIDs so that the "new" one is identical to the old.  Otherwise the API
> is unbearable...
  But when we do crazy stuff like pid namespaces these days somehow
switching pids shouldn't be *that* hard... Should it? Just a crazy idea
that occured to me now :)

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/