linux-kernel - Re: [BUG] i386 relocable kernel breakes /proc/kcore debugging

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]

Date:	Mon, 30 Jul 2007 12:32:01 +0300
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Jan Kratochvil <jan.kratochvil@...hat.com>
Cc:	Vivek Goyal <vgoyal@...ibm.com>, linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [BUG] i386 relocable kernel breakes /proc/kcore debugging

On Monday 30 July 2007 11:41, Jan Kratochvil wrote:
> On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote:
> > On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote:
>
> ...
>
> > > gdb 'thinks' that all kernel symbols are below 0x80000000 , while they
> > > are at 0xC000....
> > >
> > > Turning CONFIG_RELOCATABLE off fixes that, so I assume that is the
> > > reason for that.
> >
> > This is a gdb issue. I had raised it in gdb mailing list some time back.
> >
> > http://sourceware.org/ml/gdb/2006-08/msg00137.html
>
> There was the patch post:
> 	http://sources.redhat.com/ml/gdb/2006-08/msg00182.html
>
> > What version of gdb you are using? I know it got fixed for gdb shipped
> > with RHEL5. I am not sure about what upstream version of gdb it got fixed
> > in.
>
> It did not make it to the upstream as the patch above is an imperfect one.
> It is fixed in RH gdb-6.5-5 upwards, therefore Fedora 6 + RHEL-5.
> 	http://cvs.fedora.redhat.com/viewcvs/*checkout*/devel/gdb/gdb-6.5-bz203661
>-emit-relocs.patch?root=core
>
>
> Regards,
> Jan

Hi,

I am using mandriva 2007 and gdb that come with it ( 6.3 I think)
I also compiled gdb 6.6, but the same issue persist.

Thanks for the info, and I will try to apply the above patch and see if helps,

Will it make into gdb?

By the way, I had another issue with /proc/kcore.
That enabling sparse memory model instead of flat causes /proc/kcore not to 
work at all. I traced that to a "FIXME" in sparcemem.

/* XXX: FIXME -- wli */
#define kern_addr_valid(kaddr)  (0)

Kconfig should contatin a warning for those who select sparcemem 
that /proc/kcore will be disabled.
or maybe this should be implemented (it is not easy since spacemem allows 
memory to be discontinous, and nobody wants to allow user to read reserved 
regions)

Except the above, /proc/kcore works fine, and it is very usefull.

Best regards,
	Maxim Levitsky

Best regards,
	Maxim Levitsky
-
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/