linux-kernel - Re: Question re the disk driver for /dev/sr0

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

Message-id: <480E81E2.70704@shaw.ca>
Date:	Tue, 22 Apr 2008 18:25:06 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Question re the disk driver for /dev/sr0

Gene Heskett wrote:
> Greetings;
> 
> Has something been done to that code that is preventing /dev/sr0 from 
> correctly reporting a busy or not ready status to k3b in the last year or so?
> 
> K3B used to dutifully wait till the drive, on reloading the disc after burning 
> it, was ready to service its verify request.  Now, and for several months or 
> more, k3b attempts to read the drive immediately on the disc's being pulled 
> back in, and of course fails, causing k3b to bail out of the verify phase 
> completely.
> 
> So we are left doing it by hand, a 2 stage process, by first dividing the size 
> of the iso file being burnt by 2048 to get the number of blocks to read, and 
> then feeding dd's output for that many size 2048 blocks to sha1sum.  This 
> works fine but requires the user to understand what it is he is doing. :)

You'll need to provide more details on your setup (like what kind of 
drive and full dmesg). I haven't seen this problem.
--
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/