linux-kernel - Re: [PATCH 19/19] BLOCK: Make it possible to disable the block layer [try #6]

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060830124400.23ca9b38.akpm@osdl.org>
Date:	Wed, 30 Aug 2006 12:44:00 -0700
From:	Andrew Morton <akpm@...l.org>
To:	David Howells <dhowells@...hat.com>
Cc:	axboe@...nel.dk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 19/19] BLOCK: Make it possible to disable the block
 layer [try #6]

I think I'll just slam all this in at the first opportunity.  Stuff will
break, but it will be easy to fix.

If you try to upissue this patchset I shall be seeking an IP-routable hand
grenade.

On Tue, 29 Aug 2006 19:06:34 +0100
David Howells <dhowells@...hat.com> wrote:

> +static inline long blk_congestion_wait(int rw, long timeout)
> +{
> +	return timeout;
> +}

This function is misnamed and is implemented in the wrong place.  It's not
really a block thing at all.  If/when/soon NFS starts to implement it and
call it, things will need to be renamed and reshuffled.

Simply stubbing it out like this will cause general mayhem and CPU meltdown
all over the writeback and page-reclaim code.

So...  for now, I'll replace it with a simple io_schedule_timeout(timeout),
which is equivalent to what we do now for network filesystems.

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