Re: initrd breakage in 2.5.38-2.5.40

From: Alexander Viro (viro@math.psu.edu)
Date: Thu Oct 03 2002 - 06:07:21 EST

Next message: will fitzgerald: "Re: this code does not get called in dev.c so do we need it?"
Previous message: Alexander Viro: "Re: block device size in 2.5"
In reply to: Mikael Pettersson: "initrd breakage in 2.5.38-2.5.40"
Next in thread: Mikael Pettersson: "Re: initrd breakage in 2.5.38-2.5.40"
Reply: Mikael Pettersson: "Re: initrd breakage in 2.5.38-2.5.40"
Reply: Russell King: "Re: initrd breakage in 2.5.38-2.5.40"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 3 Oct 2002, Mikael Pettersson wrote:

> First I thought the problem was caused by a apparently missing
> set_capacity() call in 2.5.38's drivers/block/rd.c:

I _really_ doubt it - check the loop just above the add_disk() one.
set_capacity() call is done there, repeating it won't change anything.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: will fitzgerald: "Re: this code does not get called in dev.c so do we need it?"
Previous message: Alexander Viro: "Re: block device size in 2.5"
In reply to: Mikael Pettersson: "initrd breakage in 2.5.38-2.5.40"
Next in thread: Mikael Pettersson: "Re: initrd breakage in 2.5.38-2.5.40"
Reply: Mikael Pettersson: "Re: initrd breakage in 2.5.38-2.5.40"
Reply: Russell King: "Re: initrd breakage in 2.5.38-2.5.40"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:38 EST