linux-kernel - Re: Mounting sysfs early

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-prev] [day] [month] [year] [list]

Date:	Fri, 19 Jun 2009 14:36:50 +0100
From:	Will Newton <will.newton@...il.com>
To:	jim owens <jowens@...com>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Mounting sysfs early

On Fri, Jun 19, 2009 at 2:26 PM, jim owens<jowens@...com> wrote:
> Will Newton wrote:
>>
>> Hi all,
>>
>> I currently have a problem with a driver that loads firmware from
>> userland. The boot process happens in this order:
>>
>> 1. Extract initramfs
>> 2. Load drivers
>> 3. Run init
>>
>> Unfortunately it appears that step 2 is calling the hotplug helper
>> which tries to load firmware via sysfs, but sysfs is not mounted until
>> I have run init so the driver fails to initialise. What is the
>> recommended way to avoid this situation? Do I have to somehow build
>> the firmware into the kernel or can I get sysfs mounted before drivers
>> begin loading?
>
> you did not say what distro and kernel, but I would expect
> sysfs is mounted before step 2 by the intrd.  this is what I
> see in a rhel 4.3 I am testing.

I'm on an embedded board with kernel 2.6.30 booting with only an
initramfs. I should have been clearer by load drivers I mean run the
device initcalls, for example the rootfs is unpacked at initcall level
"rootfs", which is followed by device initcalls at level 6, which is
followed later by init being run. It's at this last stage that I get
sysfs mounted, which is too late, I'd like it mounted in time for
running initcall level 6. Is this possible?

> what you might be really seeing is
>
> http://bugzilla.kernel.org/show_bug.cgi?id=13178
>
> which I am currently debugging.

I don't think it's the same issue. I actually have no sysfs mounted on
/sys, it's empty.
--
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/