From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] WTF is VLI?
Date: Thu, 11 Nov 2004 13:14:30 -0800 [thread overview]
Message-ID: <20041111131430.04e96012.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0411112103060.3167-100000@localhost.localdomain>
Hugh Dickins <hugh@veritas.com> wrote:
>
> What is this "VLI" that 2.6.9 started putting after the taint string
> in i386 oopses? Vick Library Index? Vineyard Leadership Institute?
> Shall we just remove it?
>
It's a magic kaos cookie:
ksymoops handles up to 64 code bytes so dump eip-43:eip+20 with the eip
byte enclosed in <>. Add the string 'VLI ' (variable length
instructions) just before the taint output, ksymoops 2.4.8 will look
for 'VLI ' on the 'EIP:' line and split the code line into two chunks.
and
The VLI indicator tells ksymoops the dump has variable length
instructions so ksymoops splits the code into two lines at the eip byte.
Without the VLI indicator or using ksymoops < 2.4.9, ksymoops decodes the
whole line in one go.
I think the rationale is mainly so that new ksymoopses won't make a mess of
old oops records.
next prev parent reply other threads:[~2004-11-11 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 21:05 [PATCH] WTF is VLI? Hugh Dickins
2004-11-11 21:10 ` Dave Jones
2004-11-12 23:26 ` Horst von Brand
2004-11-15 21:18 ` Hugh Dickins
2004-11-16 6:00 ` Keith Owens
2004-11-16 9:56 ` Hugh Dickins
2004-11-17 5:55 ` Keith Owens
2004-11-18 15:47 ` Avi Kivity
2004-11-18 18:08 ` Horst von Brand
2004-11-18 23:38 ` Avi Kivity
2004-11-21 3:58 ` Keith Owens
2004-11-11 21:14 ` Andrew Morton [this message]
[not found] <fa.inbtt12.195ed02@ifi.uio.no>
[not found] ` <fa.cg6f09j.ji89hv@ifi.uio.no>
2004-11-18 18:28 ` Bodo Eggert
2004-11-18 23:44 ` Avi Kivity
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=20041111131430.04e96012.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hugh@veritas.com \
--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