All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Philippe Reynes <philippe.reynes@isismpp.fr>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Announce] 2.6.29-rt1
Date: Fri, 27 Mar 2009 13:04:14 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0903271236270.3397@localhost.localdomain> (raw)
In-Reply-To: <gqic7t$c27$1@ger.gmane.org>

On Fri, 27 Mar 2009, Philippe Reynes wrote:

> Hi all
> 
> I've tried to remove the mlockall(MCL_CURRENT|MCL_FUTURE)
> and now, the kernel don't crash. But a data corruption 
> appear in the data saved by the application. Such corruption
> never occurs with other kernel (2.6.28 and 2.6.29). I'll
> investigate if it could be an application bug.

I don't think that mlockall or the application is the culprit. The bug
happens in the middle of the slab cache code.

> > server calling Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT
> > MPC837x RR605
> > Modules linked in:
> > NIP: c0075b08 LR: c0075a50 CTR: c00d7d90 REGS: dbb6dcb0 TRAP: 0700   Not
> > tainted  (2.6.29-rt1) MSR: 00029032 <EE,ME,CE,IR,DR>  CR: 24002488  XER:
> > 00000000 TASK = dddea1e0[1769] 'vsftpd' THREAD: dbb6c000 GPR00: 00000001
> > dbb6dd60 dddea1e0 df803e24 df803e10 df803e08 00000000 ddc72020
> > GPR08: 00000000 0000001b dddea1e0 df803e24 24000482 100bf094 00000000
> > c04aa6fc
> > GPR16: 00200200 00100100 c04e5958 c04e595c dbb6dd68 c04e0000 c04e0000
> > c04aa6bc
> > GPR24: 00000020 dbb6ddd8 00000010 df80ae00 00000000 dbb6de38 df816800
> > df803e00
> > NIP [c0075b08] cache_alloc_refill+0x180/0x62c

addr2line -e vmlinux c0075b08
linux-2.6.29/mm/slab.c:3150

That's BUG_ON(slabp->inuse >= cachep->num);

> > LR [c0075a50] cache_alloc_refill+0xc8/0x62c
> > Call Trace:
> > [dbb6dd60] [c038878c] preempt_schedule_irq+0x5c/0x80 (unreliable)

Hmm. This one is interesting. Might be we got preempted here - which
should be fine, but who knows what we missed when we reworked the
locking.

Thanks,

	tglx

  reply	other threads:[~2009-03-27 12:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 10:54 [Announce] 2.6.29-rt1 GeunSik Lim
2009-03-27  9:37 ` Philippe Reynes
2009-03-27  9:37   ` Philippe Reynes
2009-03-27 11:10   ` Philippe Reynes
2009-03-27 12:04     ` Thomas Gleixner [this message]
2009-03-27 13:50       ` Philippe Reynes
2009-03-27 14:34         ` Philippe Reynes
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11 22:43 [Announce] 2.6.29-rc4-rt1 Thomas Gleixner
2009-02-12 22:56 ` [Announce] 2.6.29-rc4-rt2 Thomas Gleixner
2009-02-23 19:44   ` [Announce] 2.6.29-rc6-rt2 Thomas Gleixner
2009-02-24 17:51     ` Thomas Gleixner
2009-02-24 17:57       ` [Announce] 2.6.29-rc6-rt3 Thomas Gleixner
2009-03-12 19:17         ` [Announce] 2.6.29-rc7-rt1 Thomas Gleixner
2009-03-20  0:31           ` [Announce] 2.6.29-rc78rt1 Thomas Gleixner
2009-03-20 17:45             ` [Announce] 2.6.29-rc8-rt2 Thomas Gleixner
2009-03-23 16:26               ` [Announce] 2.6.29-rc8-rt3 Thomas Gleixner
2009-03-25 20:59                 ` [Announce] 2.6.29-rt1 Thomas Gleixner
2009-03-25 21:05                   ` Jaswinder Singh Rajput
2009-03-25 21:09                     ` Thomas Gleixner
2009-03-26  7:52                       ` GeunSik Lim
2009-03-26  7:52                         ` GeunSik Lim
2009-03-26  8:02                       ` GeunSik Lim
2009-03-26  8:02                         ` GeunSik Lim
2009-03-25 21:16                   ` Grammostola Rosea

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=alpine.LFD.2.00.0903271236270.3397@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=philippe.reynes@isismpp.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.