Re: arch/x86_64/kernel/traps.c:show_trace should use __kernel_text_address

Mathieu Desnoyers <[email protected]> writes:

> Hi,
> 
> I noticed arch/x86_64/kernel/traps.c:show_trace uses kernel_text_address to
> verify that an address can potentially belong to kernel code. However, this
> version takes a spinlock and should not be called from oops. I think
> __kernel_text_address would be more appropriate there.

Ok I changed it. Thanks

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- arch/x86_64/kernel/traps.c:show_trace should use __kernel_text_address
  - From: Mathieu Desnoyers <[email protected]>

Prev by Date: Re: [PATCH] THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit (ping)
Next by Date: Re: [PATCH 1/7] introduce atomic_dec_and_lock_irqsave()
Previous by thread: arch/x86_64/kernel/traps.c:show_trace should use __kernel_text_address
Next by thread: Buffer head async write
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]