mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lkml@ludenkalle.de>
To: Hugh Dickins <hugh@veritas.com>
Subject: Re: kernel BUG at include/linux/list.h:164!
Date: Sun, 2 May 2004 23:21:03 +0200	[thread overview]
Message-ID: <20040502212103.GB9447@ku-gbr.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0405020856040.14500-100000@localhost.localdomain>

Am 2004-05-02 09:22 +0100 schrieb Hugh Dickins:
> On Sat, 1 May 2004, Konstantin Kletschke wrote:
> > 
> > May  1 12:03:07 kermit kernel: kernel BUG at include/linux/list.h:164!
> > May  1 12:03:07 kermit kernel: invalid operand: 0000 [#1]
> > May  1 12:03:07 kermit kernel: PREEMPT
> > May  1 12:03:07 kermit kernel: CPU:    0
> > May  1 12:03:07 kermit kernel: EIP:    0060:[exit_rmap+237/272] Not tainted VLI
> > May  1 12:03:07 kermit kernel: EFLAGS: 00010283   (2.6.6-rc2-mm1)
> ....
> > 2.6.6-rc2-mm1 with devmapper udm1 patch
> > 
> > Is this dump due to udma1 or not and the error is fixed now?
> 
> Probably not - I don't know this udma1 patch, but the error above

It provides snapshot and pvmove functionality for LVM2 and 2.6.x
kernels and is in the early creation if I understood right...

> definitely occurs in my rmap area.

HA! :)

> though neither my testing nor anyone else has seen the same (yet).

Ok, lets see...

> I imagine you're limited in the experiments you can do on that server,
> and wouldn't want to run it with CONFIG_SLAB_DEBUG=y, which might show
> up unrelated problems - interesting for us, but troublesome for you.

Yes, sadly :(

> You're UP but PREEMPT on.  Hmm, there's a suspicious atomic_read
> in exit_rmap: once upon a time I convinced myself it was good, but
> it looks unsafe to me now - could cause a double free of an anonmm,
> which would lead to your BUG if reallocated in between.
> 
> Not so likely for me to feel this is definitely the answer, but
> likely enough to be well worth trying.  Please try patch below -
> simple enough not to make your case worse anyway - thanks.

Ok, I will try that out and incorporate the patch tomorrow. Works on
test machine fine so far (and compiles of course :P). Then we will
see, if the uptime lasts longer...

reHugh

-- 
2.6.5-mm1
Konstantin Kletschke <konsti@ludenkalle.de>, <konsti@ku-gbr.de>
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF
keulator.homelinux.org up 5:23, 18 users

      reply	other threads:[~2004-05-02 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 15:03 Konstantin Kletschke
2004-05-02  8:22 ` Hugh Dickins
2004-05-02 21:21   ` Konstantin Kletschke [this message]

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=20040502212103.GB9447@ku-gbr.de \
    --to=lkml@ludenkalle.de \
    --cc=hugh@veritas.com \
    --cc=konsti@ku-gbr.de \
    /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®