public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	Vegard Nossum <vegard.nossum@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: tty_ldisc_try_get(): BUG kmalloc-8: Poison overwritten
Date: Sun, 14 Jun 2009 14:32:51 +0200	[thread overview]
Message-ID: <20090614123251.GA14785@elte.hu> (raw)
In-Reply-To: <20090614083531.GB23149@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> --- a/drivers/char/tty_ldisc.c
> +++ b/drivers/char/tty_ldisc.c
> @@ -361,6 +361,7 @@ void tty_ldisc_deref(struct tty_ldisc *ld)
>  	unsigned long flags;
>  
>  	BUG_ON(ld == NULL);
> +	WARN_ON_ONCE(ld->refcount == (int)0xa56b6b6b);
>  
>  	spin_lock_irqsave(&tty_ldisc_lock, flags);

this does trigger:

[   70.198553] PM: Adding info for No Bus:vcsa2
[   70.223956] ------------[ cut here ]------------
[   70.233266] warning: `sudo' uses deprecated v2 capabilities in a way that may be insecure.
[   70.242894] WARNING: at drivers/char/tty_ldisc.c:364 tty_ldisc_deref+0x30/0x90()
[   70.242894] Modules linked in:
[   70.242894] Pid: 4252, comm: modprobe Not tainted 2.6.30-tip #746
[   70.242894] Call Trace:
[   70.242894]  [<413da1b0>] ? tty_ldisc_deref+0x30/0x90
[   70.242894]  [<41035c79>] warn_slowpath_common+0x49/0x60
[   70.242894]  [<41035c9d>] warn_slowpath_null+0xd/0x10
[   70.242894]  [<413da1b0>] tty_ldisc_deref+0x30/0x90
[   70.242894]  [<413d53ee>] tty_write+0x8e/0xa0
[   70.242894]  [<413d545f>] redirected_tty_write+0x5f/0x70
[   70.242894]  [<410b9002>] vfs_write+0x82/0xe0
[   70.242894]  [<413d5400>] ? redirected_tty_write+0x0/0x70
[   70.242894]  [<410b90fb>] sys_write+0x3b/0x60
[   70.242894]  [<4100388f>] sysenter_do_call+0x12/0x3c
[   70.242894]  [<4104007b>] ? timer_stats_timer_set_start_info+0xb/0x10
[   70.242894]  [<4104007b>] ? timer_stats_timer_set_start_info+0xb/0x10
[   70.242894] ---[ end trace 03c5764c731fa31f ]---
[   71.663044] device: 'vcs7': device_add

i suspect the swarm of mingetty's starting up during bootup is 
triggering some race.

	Ingo

  reply	other threads:[~2009-06-14 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14  8:10 tty_ldisc_try_get(): BUG kmalloc-8: Poison overwritten Ingo Molnar
2009-06-14  8:20 ` Pekka Enberg
2009-06-14  8:30   ` Pekka Enberg
2009-06-14  8:32     ` Pekka Enberg
2009-06-14 23:03       ` Vegard Nossum
2009-06-15  4:25         ` Pekka Enberg
2009-06-14  8:32   ` Ingo Molnar
2009-06-14  8:35     ` Ingo Molnar
2009-06-14 12:32       ` Ingo Molnar [this message]
2009-06-14 10:54 ` Alan Cox
2009-06-15  9:10   ` Catalin Marinas
2009-06-16  7:10   ` [bug] WARNING: at drivers/char/tty_io.c:1266 tty_open+0x1ea/0x388() Ingo Molnar
2009-06-16  8:44     ` Alan Cox
2009-06-16  8:49       ` Ingo Molnar
2009-06-16  9:00         ` Alan Cox
2009-06-16 19:43           ` Ingo Molnar
2009-06-16 10:13     ` Alan Cox
2009-06-16 10:24       ` Ingo Molnar

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=20090614123251.GA14785@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    --cc=vegard.nossum@gmail.com \
    /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