linux-kernel - Re: 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG

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:	Thu, 9 Nov 2006 15:13:19 -0500
From:	"Monty Montgomery" <monty@...h.org>
To:	"Jeff Garzik" <jgarzik@...ox.com>
Cc:	"Tejun Heo" <htejun@...il.com>,
	"Brice Goglin" <Brice.Goglin@...-lyon.org>,
	"Jens Axboe" <jens.axboe@...cle.com>,
	"Gregor Jasny" <gjasny@...glemail.com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, "Douglas Gilbert" <dougg@...que.net>
Subject: Re: 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG_IO)

On 11/9/06, Jeff Garzik <jgarzik@...ox.com> wrote:

> Mapping 'bidirectional' is a bit difficult.

SGIO_TO_FROM_DEVICE is *not* bdirectional!

>From the header that defines it:

#define SG_DXFER_TO_FROM_DEV -4 /* treated like SG_DXFER_FROM_DEV with the
                                   additional property than during indirect
                                   IO the user buffer is copied into the
                                   kernel buffers before the transfer */

That's pretty darned clear.  TO_FROM_DEVICE is a straight-up read.
Why the continuing confusion of what this mode is for?

> Given that there are stupid apps/libs out there in the field with this
> behavior, even if the apps are fixed I think we are stuck with the
> stupidities.

*ahem*

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