From: Davide Libenzi <davidel@xmailserver.org>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.27-05178-g2e532d6: list_add corruption
Date: Fri, 17 Oct 2008 16:19:13 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810171617490.21410@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <a4423d670810171220t4d5602fekcb66e18758149925@mail.gmail.com>
On Fri, 17 Oct 2008, Alexander Beregalov wrote:
> I am afraid I do not know how to reproduce this.
>
> WARNING: at lib/list_debug.c:30 __list_add+0x44/0x5c()
> list_add corruption. prev->next should be next (f6638448), but was
> f26f078c. (prev=f26f078c).
> Modules linked in: w83627hf hwmon_vid i2c_nforce2
> Pid: 1933, comm: rtorrent Not tainted 2.6.27-05178-g2e532d6 #6
> Call Trace:
> [<c011de4b>] warn_slowpath+0x4b/0x69
> [<c0137a03>] ? trace_hardirqs_off+0xb/0xd
> [<c01070ab>] ? native_sched_clock+0x76/0x88
> [<c0138cc5>] ? trace_hardirqs_on+0xb/0xd
> [<c0138c93>] ? trace_hardirqs_on_caller+0xe6/0x10d
> [<c031aa43>] ? release_sock+0xac/0xb4
> [<c0138cc5>] ? trace_hardirqs_on+0xb/0xd
> [<c0139d4e>] ? __lock_acquire+0xaeb/0xafa
> [<c0139d4e>] ? __lock_acquire+0xaeb/0xafa
> [<c0137a39>] ? put_lock_stats+0xd/0x21
> [<c026a404>] __list_add+0x44/0x5c
> [<c0186be0>] ep_poll_callback+0x5b/0xb4
This is very likely to be caused by a patch that went in a few days ago.
Already posted a fix to Andrew.
- Davide
next prev parent reply other threads:[~2008-10-17 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 19:20 Alexander Beregalov
2008-10-17 23:19 ` Davide Libenzi [this message]
2008-10-18 6:41 ` Alexander Beregalov
2008-10-18 14:38 ` Davide Libenzi
2008-10-18 15:50 ` Alexander Beregalov
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=Pine.LNX.4.64.0810171617490.21410@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®