From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
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: [bug] WARNING: at drivers/char/tty_io.c:1266 tty_open+0x1ea/0x388()
Date: Tue, 16 Jun 2009 09:44:30 +0100 [thread overview]
Message-ID: <20090616094430.75bbbee2@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090616071057.GA29862@elte.hu>
> > I split the ldisc and tty apart and redid the ldisc locking so its a fair
> > bet I know what changeset is to blame, will just need to hunt it down a
> > bit. kmemcheck found one leak case on Friday which I've fixed but not yet
> > scribbles.
> >
> > > c65c9bc: tty: rewrite the ldisc locking
> >
> > Almost certainly that one and will investigate on Monday
>
> I have applied your patch from yesterday (attached further below for
> reference) and the SLAB corruption has not triggered - instead i'm
> now getting this warning, after 96 reboots:
That's progress
> Another test-box has produced this warning too. (Same config and
> same hw as i sent the details for earlier in this thread.)
>
> So there's still something fishy going on.
Are you using a standard udev/fedora setup or something different (I know
the devtmpfs proposal stuff produces crashes like that one all the time
which are not seen anywhere else)
And is it reproducable this time - and always 96 ?
next prev parent reply other threads:[~2009-06-16 8:44 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
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 [this message]
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=20090616094430.75bbbee2@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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