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, 4 Oct 2008 21:05:05 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Alan Jenkins" <alan-jenkins@...fmail.co.uk>
Cc:	"Alan Jenkins" <aj504@...dent.cs.york.ac.uk>,
	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: [PATCH -tip] Tracing/fastboot: Only trace non-module initcalls

2008/10/3 Alan Jenkins <alan-jenkins@...fmail.co.uk>:
> If you want to disable non-module initcalls, then what do you have left
> that you want to trace after "Freeing unused kernel memory"?
>
> On my desktop dmesg I can see that the initramfs is loaded and started
> some time before the initcalls finish.  The initramfs includes udev
> which loads many modules; I see network, usb, sata being initialised
> before the "Freeing unused kernel memory" message.  Um...  your changes
> will _not_ stop the initcalls from these modules being shown.
>
> So I think your patch description is a bit inaccurate, and I don't
> understand what you are trying to achieve.

Hmm I'm beginning to understand what you say. Actually I didn't think
about initramfs that could launch
modules initcalls early.
It seems that modules initcalls are launched with the builtin
initcalls when one use initramfs.
Since I'm not using it, I see only the builtin initcalls before the
message of memory freeing.

I missed that point. And actually I misunderstood the real problem. My
issues with the graph happened
because of a bug in the bootgraph.pl script.
I have a patch ready that corrects it. I'm going to post it and
explain the real problem.

Thanks Alan!
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ