mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: acahalan@cs.uml.edu (Albert D. Cahalan)
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: silly [< >] and other excess
Date: Thu, 23 Nov 2000 07:53:24 +0000 (GMT)	[thread overview]
Message-ID: <200011230753.eAN7rOt14124@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200011230254.eAN2sm9158656@saturn.cs.uml.edu> from "Albert D. Cahalan" at Nov 22, 2000 09:54:48 PM

Albert D. Cahalan writes:
> > they are not only references to
> > kernel functions, but also kernel data and read only data within
> > the kernel text segment.
> 
> 1. this is harmless
> 2. this is useful (you might get a variable's name)

Wrong.  Op-codes on this machine are organised such that bits 31-28
indicate the "condition" that the instruction executes.  All 16
combinations are meaningful.  This means that any 32-bit value can
appear to be an instruction OR data.  It takes human intellect to
decide which it is.  No machine can tell you that.

> Nope. You get the unmolested oops and some symbol data.
> If there isn't any symbol for 0x424a5149, so what? It is
> no big deal to look up a few opcodes in the symbol table
> by accident.

But there could well be a symbol for 0xc0023004, but it also
corresponds to the instruction:

	andgt   r3, r2, r4

"Perform a logical AND operation between r2 and r4 and place the result
 in r3 if the condition codes indicate the `Greater Than' condition"

In addition, the kernel may not be compiled to run at address 0xC.......
but at address 0x6....... or maybe even 0xe.......  Guess what 0xE means
in the high nibble of the op-code?  "Always", or "Unconditional".

> That would be trading one design flaw for another.
> 
> The hard part of klogd/ksymoops is decoding the code bytes AFAIK.
> The rest is a just a cross between grep and ps -- you search and
> you do symbol lookups. I could throw it together in a few hours,
> minus the disassembly part.

As far as I am concerned, you are the people who propose to break
something, and therefore you are the people who should provide the
effort to fix what you will be breaking when the brokenness is
highlighted.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         Russell King        rmk@arm.linux.org.uk      --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-23 18:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 19:00 Andries.Brouwer
2000-11-22 23:16 ` Russell King
2000-11-22 23:54   ` Albert D. Cahalan
2000-11-23  0:10     ` Russell King
2000-11-23  2:54       ` Albert D. Cahalan
2000-11-23  3:03         ` Keith Owens
2000-11-23 12:39           ` Albert D. Cahalan
2000-11-23 12:46             ` Alan Cox
2000-11-23 19:46             ` Russell King
2000-11-23  7:53         ` Russell King [this message]
2000-11-25  4:33           ` Albert D. Cahalan
2000-11-25  9:17             ` Russell King
2000-11-25 10:26               ` Albert D. Cahalan
2000-11-25 11:07                 ` Keith Owens
2000-11-25 12:18                   ` Albert D. Cahalan
2000-11-25 18:20                   ` silly [< >] Guest section DW
2000-11-24  8:09                     ` Pavel Machek
2000-11-25 12:11                 ` silly [< >] and other excess Russell King
2000-11-27 22:02                   ` Peter Samuelson
2000-11-27 22:35                     ` Keith Owens
2000-11-27 23:01                       ` bread in fat_access failed Nerijus Baliunas
2000-11-27 23:11                         ` Nerijus Baliunas
2000-11-28  9:16                       ` silly [< >] and other excess Christian Gennerat
2000-11-23  0:26     ` Russell King
2000-11-23  3:11       ` Ragnar Hojland Espinosa
2000-11-23  7:55         ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2000-11-23  2:24 Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16   ` Tuomas Heino
2000-11-23  0:38 Andries.Brouwer
2000-11-23  0:51 ` Alan Cox
2000-11-22 13:20 [PATCH] isofs/inode.c Andries.Brouwer
2000-11-22 13:42 ` silly [< >] and other excess Christian Gennerat
2000-11-22 16:00   ` Russell King
2000-11-22 22:22   ` Keith Owens
2000-11-22 23:32     ` Albert D. Cahalan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200011230753.eAN7rOt14124@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®