| 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
| ||
|
Date: Wed, 30 May 2012 16:00:43 -0700 From: Dan Williams <dan.j.williams@...el.com> To: walt <w41ter@...il.com> Cc: linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org Subject: Re: [PATCH v2] scsi: fix async probe regression On Tue, May 29, 2012 at 5:53 PM, walt <w41ter@...il.com> wrote: > On 05/25/2012 10:55 AM, Dan Williams wrote: >> Commit a7a20d1 "[SCSI] sd: limit the scope of the async probe domain" >> moved sd probe work out of reach of wait_for_device_probe(). Allow it >> to be synced via scsi_complete_async_scans(). > > Hi Dan. After applying version 2 of a7a20d1 I can boot again, but there's > a catch :) Ah you took me off the cc, so I missed this originally. > > My grub.cfg boot menu entry uses the root=PARTUUID=<guid> syntax, but that > has stopped working. After a7a20d1(v2) I have to use root=/dev/sda5 or I > get the familiar "can't find block device (foo,bar)" kernel panic. What is a7a20d1(v2)? That's the original commit that broke things, so I'm confused. > Any idea what would cause that particular kind of breakage? The fix should be equivalent for both root= options because if the device can be found by /dev/sda5 I don't see anything related to the async subsystem that would prevent it from being looked up by uuid?? -- Dan -- 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