linux-kernel - Re: 2.6.23-mm1 s390 driver problem

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: <1192780036.25150.7.camel@localhost>
Date:	Fri, 19 Oct 2007 09:47:16 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>
Cc:	Christian Borntraeger <borntraeger@...ibm.com>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	cornelia.huck@...ibm.com, heiko.carstens@...ibm.com,
	sam@...nborg.org
Subject: Re: 2.6.23-mm1 s390 driver problem

On Thu, 2007-10-18 at 15:31 -0500, Serge E. Hallyn wrote:
> Quoting Christian Borntraeger (borntraeger@...ibm.com):
> > Am Donnerstag, 18. Oktober 2007 schrieb Serge E. Hallyn:
> > > Sigh, well this turned out less informative than I'd liked.
> > > After bisecting 2.6.23 to 2.6.23-mm1, I found that
> > > git-s390.patch is the one breaking my s390 boot :(
> > > (Frown bc it's a conglomeration of patches0
> > > 
> > > Symptom is:
> > > 	"Cannot open root device "dasdd2" or unknown-block(94,14)"
> > > even though dasdd2 appeared to be found earlier in the boot.  I also
> > > get
> > 
> > Can you post the full console output from IPL to the unsuccessful end?
> 
> Yeah, sorry, appended below.
> 
> I had thought that the line
> 	sysctl table check failed: /sunrpc/transports .7249.14 Missing strategy
> meant that the fix referenced in http://lkml.org/lkml/2007/10/11/48
> would fix it, but it appeared to have no effect.

This is the vmlinux.lds.S problem. The cleanup patch from Sam Ravnborg
moved the __initramfs_start and __initramfs_end symbols into
the .init.ramfs section. This is in itself not a problem, but it
surfaced a bug: there is no *(.init.initramfs), that needs to be
*(init.ramfs). I corrected this in the upstream patch but 2.6.23-mm1 has
the older one that still causes the "Cannot open root device". For
2.6.23-mm1 use the patch below.

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.

---
diff -urpN linux-2.6/arch/s390/kernel/vmlinux.lds.S linux-2.6-patched/arch/s390/kernel/vmlinux.lds.S
--- linux-2.6/arch/s390/kernel/vmlinux.lds.S	2007-10-19 09:41:57.000000000 +0200
+++ linux-2.6-patched/arch/s390/kernel/vmlinux.lds.S	2007-10-19 09:42:29.000000000 +0200
@@ -128,7 +128,7 @@ SECTIONS
 	. = ALIGN(0x100);
 	.init.ramfs : {
 		__initramfs_start = .;
-		*(.init.initramfs)
+		*(.init.ramfs)
 		. = ALIGN(2);
 		__initramfs_end = .;
 	}


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