linux-kernel - Re: [RFC PATCH 00/22] loop: Issue O

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: <x49obsgawoo.fsf@segfault.boston.devel.redhat.com>
Date:	Thu, 01 Mar 2012 15:33:11 -0500
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Zach Brown <zab@...bo.net>,
	Dave Kleikamp <dave.kleikamp@...cle.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 00/22] loop: Issue O_DIRECT aio with pages

Christoph Hellwig <hch@...radead.org> writes:

> On Tue, Feb 28, 2012 at 10:14:34AM -0500, Zach Brown wrote:
>> Yeah, that's reasonable.  Perhaps obviously, we started with new entry
>> points to minimize the amount of churn we'd have to go through to test
>> the change in behaviour.
>> 
>> It's going to be messy to try and abstract away the pinning and dirtying
>> of the iter regions from direct IO through the iter interface, but maybe
>> not horribly so.
>
> I don't really care to much about the implementation inside fs/direct-io.c
> (at least for now - once I see it I might still scream "bloody
> murder!").
>
> The point is to pass the iov_iter all the way down to a common entry
> point in fs/direct-io.c, so that the filesystems don't have to care
> for that difference.

I started reviewing, but I think I'll hold off until the next posting.
Dave, what was the original subject of the thread from Zach back in '09?
That spinics link isn't working for me anymore, and I'd like to go back
over my review comments from back then.

Cheers,
Jeff
--
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/