From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Brian Phelps" <lm317t@gmail.com>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>
Cc: linux-kernel@vger.kernel.org, "Al Viro" <viro@zeniv.linux.org.uk>,
"Mikael Pettersson" <mikpe@it.uu.se>,
"Alexander Shaduri" <ashaduri@gmail.com>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: kernel BUG at mm/slab.c:601
Date: Sat, 22 Nov 2008 02:26:52 +0100 [thread overview]
Message-ID: <19f34abd0811211726h143c83f6obdfcb97e71fa595f@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0811211725s169dc42ao195c61b6dac3e975@mail.gmail.com>
[Resend with (I hope) working e-mail address for Mauro]
On Sat, Nov 22, 2008 at 2:25 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Sat, Nov 22, 2008 at 2:10 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>>> [ 527.562373] ffffffff8043b157 0000000000200200 ffffffffa02810d4
>>> ffff88001e13c600
>>
>> LIST_POISON2 on the stack:
>>
>> include/linux/poison.h:#define LIST_POISON2 ((void *) 0x00200200)
>
> So looking at bttv source code, I wonder what the codes like these are
> trying to do:
>
> if (set->top->vb.queue.next)
> list_del(&set->top->vb.queue);
>
> Code is ancient, I'll ask Mauro.
>
>
> Vegard
>
> --
> "The animistic metaphor of the bug that maliciously sneaked in while
> the programmer was not looking is intellectually dishonest as it
> disguises that the error is the programmer's own creation."
> -- E. W. Dijkstra, EWD1036
>
next prev parent reply other threads:[~2008-11-22 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 23:24 Brian Phelps
2008-11-19 13:40 ` Brian Phelps
2008-11-19 22:19 ` Vegard Nossum
2008-11-20 17:01 ` Brian Phelps
2008-11-22 1:10 ` Vegard Nossum
2008-11-22 1:25 ` Vegard Nossum
2008-11-22 1:26 ` Vegard Nossum [this message]
2008-11-22 1:50 ` Vegard Nossum
2008-11-22 11:20 ` [PATCH] bttv: don't compare list_head's .next with NULL Vegard Nossum
2008-11-24 17:13 ` Brian Phelps
2008-11-24 10:39 ` kernel BUG at mm/slab.c:601 Mauro Carvalho Chehab
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=19f34abd0811211726h143c83f6obdfcb97e71fa595f@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=adobriyan@gmail.com \
--cc=ashaduri@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm317t@gmail.com \
--cc=mchehab@infradead.org \
--cc=mikpe@it.uu.se \
--cc=rjw@sisk.pl \
--cc=viro@zeniv.linux.org.uk \
/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®