linux-kernel - Re: Scatter-gather list constraints

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: <20080620.135006.243389159.davem@davemloft.net>
Date:	Fri, 20 Jun 2008 13:50:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	stern@...land.harvard.edu
Cc:	linux-kernel@...r.kernel.org, antonio.lin@...ormicro.com,
	david.vrabel@....com
Subject: Re: Scatter-gather list constraints

From: Alan Stern <stern@...land.harvard.edu>
Date: Fri, 20 Jun 2008 16:30:25 -0400 (EDT)

> This question arises in connection with wireless USB mass-storage
> devices.  The controller driver requires that all DMA segments
> in a transfer, other than the last one, have a multiple of 1024 bytes.  
> But we're sometimes getting s-g lists where an element contains an odd
> number of 512-byte sectors, and of course it doesn't work.

The generic device layer DMA bits does have ways to indicate
DMA restrictions such as maximum segment size, but not something
like this.

This is a pretty strange requirement, and would be probably be
quite difficult to support across the board just to handle this
strange device :)
--
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/