linux-kernel - Re: [PATCH 04/26] aio: remove retry-based AIO

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

Message-ID: <CAJd=RBBAcZXKZZSrMuzm963ie81oGjHzYgyogtr2SPW2E0E_0w@mail.gmail.com>
Date:	Wed, 19 Dec 2012 20:04:11 +0800
From:	Hillf Danton <dhillf@...il.com>
To:	Kent Overstreet <koverstreet@...gle.com>
Cc:	Zach Brown <zab@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
	Hillf Danton <dhillf@...il.com>
Subject: Re: [PATCH 04/26] aio: remove retry-based AIO

>@@ -52,15 +46,6 @@ struct kioctx;
>  * not ask the method again -- ki_retry must ensure forward progress.
>  * aio_complete() must be called once and only once in the future, multiple
>  * calls may result in undefined behaviour.
>- *
>- * If ki_retry returns -EIOCBRETRY it has made a promise that kick_iocb()
>- * will be called on the kiocb pointer in the future.  This may happen
>- * through generic helpers that associate kiocb->ki_wait with a wait
>- * queue head that ki_retry uses via current->io_wait.  It can also happen
>- * with custom tracking and manual calls to kick_iocb(), though that is
>- * discouraged.  In either case, kick_iocb() must be called once and only
>- * once.  ki_retry must ensure forward progress, the AIO core will wait
>- * indefinitely for kick_iocb() to be called.
>  */
> struct kiocb {
> 	struct list_head	ki_run_list;

Then you can also erase ki_run_list if no longer used.

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