linux-kernel - Re: BAD_SG_DMA panic in aha1542

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]

Date:	Mon, 30 Apr 2007 19:32:45 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	James Bottomley <James.Bottomley@...elEye.com>
Cc:	Bob Tracy <rct@...rkin.frus.com>, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, hch@...radead.org
Subject: Re: BAD_SG_DMA panic in aha1542

On Fri, Apr 27 2007, James Bottomley wrote:
> > sgpnt[0:1] page c1ee5af0/0x1ee5af0 length 32
> > Kernel panic - not syncing: Buffer at physical address > 16 Mb used for aha1542
> > 
> > As before, no problems using the sda hard disk (which is the boot drive):
> > everything works reliably until I touch the cdrom drive.
> > 
> > I'll be happy to assist with the debugging, but the system with the
> > aha1542 has no development facilities, i.e., I'll have to build test
> > kernels on a different system, and turnaround is going to be slow :-(.
> 
> I'm interested.
> 
> This is clearly a use_sg==1 path that has failed to bounce the buffer
> for some reason ... and I was contemplating eliminating the GFP_DMA from
> our sr driver because I thought the block bouncing had it covered.
> 
> It might also be helpful to apply this patch.  It should give a stack
> trace of the problem command and not immediately panic the box.

It's due to the crappy ->generic_packet() ioctl stuff, it bypasses the
block layer. So that needs to be converted to use block pc requests and
the block layer interface, then things will just work.

Christoph had a sort-of ready patch for that some time ago. Christoph,
did that ever materialize into a full blown patch?

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