linux-kernel - Re: [PATCH 2/5] aio: kiocb

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:	Wed, 10 Oct 2012 19:21:51 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Zach Brown <zab@...hat.com>
Cc:	Kent Overstreet <koverstreet@...gle.com>,
	linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
	dm-devel@...hat.com
Subject: Re: [PATCH 2/5] aio: kiocb_cancel()

On Wed, Oct 10, 2012 at 02:20:51PM -0700, Zach Brown wrote:
> 
> I sympathize, but the reality is that the current infrastructure
> is very bad and no one is using it.
> 
> It's not like we're getting rid of the syscall.  I'll be behaving
> exactly as it does today: returning the error code that indicates that
> cancellation failed because it lost the race with completion.  Every
> caller has to cope with that to use cancel safely.

Yes, I realize it doesn't work today.  But hopefully we'll be able to
reimplement it in a cleaner way.  That's why I said, I hope we don't
give up on the functionality of aio_cancel --- not that I'm against
removing what we currently have.

Cheers,

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