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: <15995.1156854308@warthog.cambridge.redhat.com>
Date:	Tue, 29 Aug 2006 13:25:08 +0100
From:	David Howells <dhowells@...hat.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Chris Wedgwood <cw@...f.org>, David Howells <dhowells@...hat.com>,
	axboe@...nel.dk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/18] [PATCH] BLOCK: Don't call block_sync_page() from AFS [try #4] 

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

> AFS never sets a backing_dev_info on it's own and thus uses
> &default_backing_dev_info which sets the unplug_io_fn to
> default_unplug_io_fn.  default_unplug_io_fn is a no-op, and thus
> block_sync_page does nothing for AFS.

I'm sure I used to require this for when there was a local cache on disk.
Maybe things have changed, or maybe I'm misremembering.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ