linux-kernel - Re: 3.8.3 build error, compiler segfault

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

Date:	Sat, 30 Mar 2013 06:25:49 -0400
From:	Tom H <tomh0665@...il.com>
To:	Ubuntu Users <ubuntu-users@...ts.ubuntu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 3.8.3 build error, compiler segfault

On Fri, Mar 29, 2013 at 9:27 AM, Gene Heskett <gheskett@...v.com> wrote:
> On Friday 29 March 2013 09:08:27 Tom H did opine:
>
> CCing the lkml too.
>
>> On Thu, Mar 28, 2013 at 10:49 AM, Nils Kassube <kassube@....net> wrote:
>>> I don't know of a particilar tool to extract that info. I can't tell
>>> you for your -rtai kernel but the standard Ubuntu kernels come with a
>>> file /boot/config-$(uname -r) which is the .config from the kernel
>>> build. There you could search for '=y', but it would list more than
>>> only parts which can be compiled either as module or built-in. I
>>> checked the contents of the initrd and it seems the file /etc/modules
>>> isn't included there. Obviously it is run later in the boot sequence,
>>> not from the initrd. Sorry for that misleading suggestion.
>>>
>>>...
>>>
>>> While it looks right, I don't think it will help because the contents
>>> of /etc/modules doesn't seem to be included in the initrd anyway (see
>>> above).
>>
>> /etc/initramfs-tools/modules
>
> And that brings up a chicken/egg problem, as in if it can't access that
> UUID containing /etc/modules, how does it read it to find out its supposed
> to do early early loads of sata_nv, and possibly i2c_nforce even if they
> are in the generated initrd?

There's no chicken and egg. "/etc/initramfs-tools/modules" isn't
"/etc/modules". Having your module listed there'll ensure that it's
loaded in the initrd once you re-run mkinitramfs or update-initramfs.
--
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/