linux-kernel - Re: [bug] latest -git boot hang

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: <48F3113F.7090905@kernel.org>
Date:	Mon, 13 Oct 2008 18:13:35 +0900
From:	Tejun Heo <tj@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [bug] latest -git boot hang

H. Peter Anvin wrote:
> Tejun Heo wrote:
>>
>> Yeap, if fedora didn't work, I think it should be hidden.  Do we already
>> have place to hide things like this?
>>
> 
> By the way, I don't see anything in this patchset that lets userspace
> discover the parent device.  Since the old rule of
> 
>     partition device = parent device + partition number
> 
> ... no longer holds, this is a serious omission for something that is in
> mainstream (and therefore *requires* that a new interface is deployed
> for anything that cares.)
> 
> This will have to be addressed before 2.6.28 final.

The sysfs directory for the parent can be reached by "cd -P
/sys/class/block/PART/..".  That should be enough, right?  I'll add
the partition attribute but I don't really think we need to do
anything to improve parent discovery.

Thanks.

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