Linux-kernel mailing list archive 2000-26,: Re: spinlocks() are severely broken in 2.2.X and 2.4.X for modules

# Re: spinlocks() are severely broken in 2.2.X and 2.4.X for modules

Andi Kleen (ak@suse.de)
Sat, 1 Jul 2000 14:47:37 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: James Simmons: "Re: console_lock too early in printk???"
- Previous message: Michael Borrelli: "Re: Low Latency Patch"

On Sat, Jul 01, 2000 at 02:32:15PM +0200, Andi Kleen wrote:
> On Sat, Jul 01, 2000 at 11:59:11AM +0200, Manfred Spraul wrote:
> > Andi Kleen wrote:
> > >
> > > I had it happen to me in the past too for my sysctl rewrite. In this
> > > case it happened in the main kernel for a .sysctl -> .data relocation.
> > > It happened in the main vmlinux. It seems to require some complex
> > > input to trigger (it is not as simple as intersegment relocation does not
> > > work). In my case I had a few hundred relocations and one was wrong
> > > and caused crashes.
> > >
> >
> > Is it possible to detect the problem automatically until binutils is
> > fixed? (objdump + script)
>
> Here is a quick hack. The results are slightly off because of section
> padding though. It only works on object files or modules (vmlinux doesn't
> have any reloc records)

[...]

Ok, it breaks with semaphores too. That probably explains the off-ness.

Also of course it only makes sense to run it with kernel modules that went
through ld -r

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: James Simmons: "Re: console_lock too early in printk???"
- Previous message: Michael Borrelli: "Re: Low Latency Patch"