linux-kernel - RE: in 2.6.23-rc3-git7 in do_cciss

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 for Android: free password hash cracker in your pocket

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

Message-ID: <0F5B06BAB751E047AB5C87D1F77A7788413663D229@GVW0547EXC.americas.hpqcorp.net>
Date:	Thu, 4 Sep 2008 18:00:18 +0000
From:	"Miller, Mike (OS Dev)" <Mike.Miller@...com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	James Bottomley <James.Bottomley@...senpartnership.com>,
	lkml <linux-kernel@...r.kernel.org>,
	scsi <linux-scsi@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>,
	Jens Axboe <jens.axboe@...cle.com>
Subject: RE: in 2.6.23-rc3-git7 in do_cciss_intr

> >>> 0x3bb2 <do_cciss_intr+1649>:    mov    0x2(%r8),%dx
> >>> 0x3bb7 <do_cciss_intr+1654>:    test   %dx,%dx
> >>> 0x3bba <do_cciss_intr+1657>:    je     0x3f0e <do_cciss_intr+2509>
> >>>
> >>>
> >>> $ addr2line -e cciss.o -f  do_cciss_intr+0x627 SA5_fifo_full
> >>>
> /home/rdunlap/linsrc/linux-2.6.27-rc3-git7/drivers/block/cciss.h:206
> >> OK ...that's confusing.  It seems to be saying that ctrlr_info_t *
> >> was NULL.  However, I can't see a way of getting into the
> fifo_full
> >> callback from do_cciss_intr ..
> >> especially not with an NULL host.
> >>
> >> James
> >
> > That is weird. Even if we could get there fifo_full doesn't
> do anything but wait for a bit.
>
> Hi,
>
> This just happened again.  This time it's on 2.6.27-rc5-git3.
>
> ~Randy

Thanks Randy. I think. :)

I'll try to recreate in my lab.

-- mikem
>
--
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/