linux-kernel - Re: cdparanoia not setting count and/or reply

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] [day] [month] [year] [list]

Message-ID: <20070709113025.GB3015@DervishD>
Date:	Mon, 9 Jul 2007 13:30:25 +0200
From:	DervishD <lkml@...vishd.net>
To:	Douglas Gilbert <dougg@...que.net>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Linux-kernel <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org
Subject: Re: cdparanoia not setting count and/or reply_len properly

    Hi Douglas :)

 * Douglas Gilbert <dougg@...que.net> dixit:
> >>     I don't know if cdparanoia should be fixed, but certainly the
> >> warning could be issued only if CONFIG_SCSI_VERBOSE is set. This way you
> >> will have the message if something goes wrong and you want more info,
> >> but in cases where the warning is harmless your log will be clean...
> >>
> >>     Anyway, this message is not for make suggestions, but for asking for
> >> information: why is this warning happening? naugthy cdparanoia? naughty
> >> kernel? I'm a bit confused and I want to use my external DVD drive for
> >> ripping from time to time, to "exercise" it...
> 
> In Fedora 7 I see this:
> 
> # cdparanoia --version
> cdparanoia III release 9.8 (March 23, 2001)
> (C) 2001 Monty <monty@...h.org> and Xiphophorus

    Same version here.

> So, given that date, lk 2.4.2 was out but it was probably
> a bit early to start using the sg version 3 interface
> which first appeared in lk 2.4.1 . So that "lets annoy
> the user" message was added by someone who got burnt by
> the old sg version 2 interface and decided people needed
> to be warned. The warning comes from this code is sg.c :

    OK, grand. So it's cdparanoia's fault.

>         /*
>          * SG_DXFER_TO_FROM_DEV is functionally equivalent to SG_DXFER_FROM_DEV,
>          * but is is possible that the app intended SG_DXFER_TO_DEV, because the
> re
>          * is a non-zero input_size, so emit a warning.
>          */
>         if (hp->dxfer_direction == SG_DXFER_TO_FROM_DEV)
>                 if (printk_ratelimit())
>                         printk(KERN_WARNING
>                                "sg_write: data in/out %d/%d bytes for SCSI comma
> nd 0x%x--"
>                                "guessing data in;\n" KERN_WARNING "   "
>                                "program %s not setting count and/or reply_len pr
> operly\n",
>                                old_hdr.reply_len - (int)SZ_SG_HEADER,
>                                input_size, (unsigned int) cmnd[0],
>                                current->comm);

    Yes, I did read the code, and I didn't find any reason for it to
exist, but I didn't understand the purpose of SG_DXFER_TO_FROM_DEV.
Thanks for explaining this :))

> It is probably about time that cdparanoia was updated ...

    I think the same, but given that it works, Monty probably doesn't
have much motivation to update it. I don't know if the problem resides
in the cdparanoia program itself (so using the DAE problem from cdrkit
will fix the issue) or in the paranoia library. In this case, the
problem will affect any program using the library.

    Anyway, if you need any testing, just tell :)

    Thanks a lot!

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
-
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/