From: Randy Dunlap <randy.dunlap@oracle.com>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc1 (scsi_debug: list corruption)
Date: Thu, 04 Nov 2010 09:12:21 -0700 [thread overview]
Message-ID: <4CD2DB65.5060400@oracle.com> (raw)
In-Reply-To: <AANLkTin5PphTtZaesEU3U0PA8NJv=Jmis8yQF6b=KbeG@mail.gmail.com>
On 11/03/10 19:25, Xiaotian Feng wrote:
> On Thu, Nov 4, 2010 at 7:20 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>
>>
>> [ 102.555847] calling scsi_debug_init+0x0/0x704 [scsi_debug] @ 3337
>> Nov 3 16:06:12 control kernel: [ 102.555847] calling scsi_deb[ 102.622974] scsi_debug: host protection
>> [ 102.627513] scsi4 : scsi_debug, version 1.82 [20100324], dev_size_mb=8, opts=0x0
>> Nov 3 16:06:13 control kernel: [ 102.639095] initcall scsi_debug_init+0x0/0x704 [scsi_debug] returned 0 after 75039 usecs
>> Nov 3 16:06:13 [ 102.651072] ------------[ cut here ]------------
>> [ 102.657373] WARNING: at /local/linsrc/lnx-2637-rc1/lib/list_debug.c:26 __list_add+0x4d/0xa5()
>> [ 102.666012] Hardware name: OptiPlex GX620
>> [ 102.671396] list_add corruption. next->prev should be prev (ffffffff81ae5e50), but was 6b6b6b6b6b6b6b6b. (next=ffff88006c880590).
>
> This might be related with net rds percpu_counter corruption. Does
> following patch fix your issue?
> http://patchwork.ozlabs.org/patch/69939/
Yes, somehow that patch fixes it.
What good eyes you have.
thanks,
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-11-04 16:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 12:07 Linux 2.6.37-rc1 Linus Torvalds
2010-11-01 15:37 ` Thomas Gleixner
2010-11-01 15:47 ` Nick Bowler
2010-11-01 15:52 ` Ryusuke Konishi
2010-11-01 16:07 ` Linus Torvalds
2010-11-02 18:51 ` Linux 2.6.37-rc1 (acpi_video) Randy Dunlap
2010-11-03 21:08 ` Linux 2.6.37-rc1 (cciss: remove_proc_entry warning) Randy Dunlap
2010-11-03 21:15 ` Linux 2.6.37-rc1 (pcrypt fault) Randy Dunlap
2010-11-10 11:21 ` Steffen Klassert
2010-11-10 18:11 ` Randy Dunlap
2010-11-03 21:21 ` Linux 2.6.37-rc1 (net/sched: cls_cgroup) Randy Dunlap
2010-11-03 22:01 ` Eric Dumazet
2010-11-03 22:19 ` Li Zefan
2010-11-03 22:31 ` Li Zefan
2010-11-03 23:31 ` Herbert Xu
2010-11-04 1:46 ` Li Zefan
2010-11-04 1:56 ` David Miller
2010-11-04 15:56 ` Randy Dunlap
2010-11-03 23:16 ` Linux 2.6.37-rc1 (floppy module load: no device found) Randy Dunlap
2010-11-05 22:10 ` Linus Torvalds
2010-11-05 22:12 ` David Miller
2010-11-05 23:03 ` Randy Dunlap
2010-11-05 23:36 ` Linus Torvalds
2010-11-06 0:33 ` Randy Dunlap
2010-11-06 12:16 ` Vivek Goyal
2010-11-06 14:52 ` Linus Torvalds
2010-11-03 23:18 ` Linux 2.6.37-rc1 (libipw remove_proc_entry warning) Randy Dunlap
2010-11-05 22:24 ` Linus Torvalds
2010-11-05 23:06 ` Randy Dunlap
2010-11-05 23:38 ` Linus Torvalds
2010-11-08 21:33 ` John W. Linville
2010-11-03 23:20 ` Linux 2.6.37-rc1 (scsi_debug: list corruption) Randy Dunlap
2010-11-04 2:25 ` Xiaotian Feng
2010-11-04 16:12 ` Randy Dunlap [this message]
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=4CD2DB65.5060400@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xtfeng@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