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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 5 Sep 2008 11:28:38 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	"Miller, Mike (OS Dev)" <Mike.Miller@...com>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	lkml <linux-kernel@...r.kernel.org>,
	scsi <linux-scsi@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: in 2.6.23-rc3-git7 in do_cciss_intr

On Thu, Sep 04 2008, Miller, Mike (OS Dev) wrote:
> > >>> 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.

This looks somewhat strange, mostly like 'c' is NULL and it's oopsing in
in removeQ (I don't think Randy's analysis is correct in assuming it's
'h' and it's in fifo_full). Given that 'c' cannot be NULL, it's c->prev
or c->next that are NULL.

-- 
Jens Axboe

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