linux-kernel - Re: 2.6.27-05178-g2e532d6: list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0810171617490.21410@alien.or.mcafeemobile.com>
Date:	Fri, 17 Oct 2008 16:19:13 -0700 (PDT)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Alexander Beregalov <a.beregalov@...il.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: 2.6.27-05178-g2e532d6: list_add corruption

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/