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: <515EE63A.6050307@cip.cs.fau.de>
Date:	Fri, 05 Apr 2013 16:56:58 +0200
From:	Sebastian Wankerl <sisewank@....cs.fau.de>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	linux-kernel@...r.kernel.org,
	Philip Kranz <philip.kranz@...glemail.com>,
	i4passt@...ts.informatik.uni-erlangen.de
Subject: Re: [PATCH] Add non-zero module sections to sysfs

On 04/05/13 06:00, Rusty Russell wrote:
> Sebastian Wankerl <sisewank@....cs.fau.de> writes:
>> On 04/04/13 03:00, Rusty Russell wrote:
>>> Sebastian Wankerl <sisewank@....cs.fau.de> writes:
>>>> Add non-zero module sections to sysfs on architectures unequal to PARISC.
>>>> KGDB needs all module sections for proper module debugging. Therefore, commit 
>>>> 35dead4235e2b67da7275b4122fed37099c2f462 is revoked except for PARISC
>>>> architecture.
>>> #ifdef CONFIG_PARISC in the middle of kernel/module.c is super-ugly, and
>>> wrong.
>> I don't see why this is wrong. It used to load all sections to sysfs
>> until the patch mentioned. Actually, it is the PARISC build chain which
>> is broken.

We worked on that topic further. Now we have another suggestion: would
it be okay to add a field to struct module for use by kgdb where we save
the section names for our use. This seems to be the most valuable
solution as solving the sysfs stuff is rather hard.
--
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