linux-kernel - Re: [PATCH 05/18] [PATCH] BLOCK: Don't call block_sync

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: <9824.1156842031@warthog.cambridge.redhat.com>
Date:	Tue, 29 Aug 2006 10:00:31 +0100
From:	David Howells <dhowells@...hat.com>
To:	Chris Wedgwood <cw@...f.org>
Cc:	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] 

Chris Wedgwood <cw@...f.org> wrote:

> > The AFS filesystem specifies block_sync_page() as its sync_page
> > address op, which needs to be checked, and so is commented out for
> > the moment.
> 
> Wouldn't it be better to just let the link/build fail so someone who
> groks AFS internals can look into this?

That would be me...

I don't want the block patches getting rejected because make allyesconfig fails
due to AFS not linking.

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/