| 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
| ||
|
Date: Tue, 13 Feb 2007 14:57:29 -0500 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: Joel Soete <soete.joel@...rlet.be> Cc: Tejun Heo <htejun@...il.com>, Luming Yu <luming.yu@...il.com>, Alan Cox <alan@...hat.com>, Ioan Ionita <opslynx@...il.com>, Alan <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org, jgarzik@...ox.com Subject: Re: 2.6.20-rc6 libata PATA ATAPI CDROM is not working On Tue, Feb 13, 2007 at 05:35:32PM +0000, Joel Soete wrote: > A small update: > your patch also works against 2.6.20 > > but seems that open the door to numerous other pb: > 1/ pb to burn cd: > # md5sum cd060213.iso > 6a1248783a21722816b972aa9bae9d5e cd060213.iso > > # ll cd060213.iso > -rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso > > # dd if=/dev/sr0 bs=1 count=3213312 | md5sum > dd: reading `/dev/sr0': Input/output error > 0337e9846d17779945c5c252d4f897f0 - > 3129344+0 records in > 3129344+0 records out > 3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s > > eventhought cdrecord seems to be successfull??? Has that ever worked by any method? I have always had to use readcd along with passing the correct number of sectors on the CD to get a proper matching image. dd always seems to end up reading some junk past the end of the disc. > 2/ (but that should be much more related to scsi api) sdcXX > sdc15 doesn't > works ;-( > # sfdisk -l /dev/sdc > > Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End #cyls #blocks Id System > /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32 > /dev/sdc2 196 1825 1630 13092975 5 Extended > /dev/sdc3 0 - 0 0 0 Empty > /dev/sdc4 0 - 0 0 0 Empty > /dev/sdc5 * 196+ 197 2- 16033+ 83 Linux > /dev/sdc6 * 198+ 199 2- 16033+ 83 Linux > /dev/sdc7 200+ 201 2- 16033+ 83 Linux > /dev/sdc8 202+ 217 16- 128488+ 82 Linux swap / Solaris > /dev/sdc9 218+ 478 261- 2096451 83 Linux > /dev/sdc10 479+ 486 8- 64228+ 83 Linux > /dev/sdc11 487+ 488 2- 16033+ 83 Linux > /dev/sdc12 489+ 504 16- 128488+ 83 Linux > /dev/sdc13 505+ 618 114- 915673+ 83 Linux > /dev/sdc14 619+ 620 2- 16033+ 83 Linux > /dev/sdc15 621+ 636 16- 128488+ 83 Linux > /dev/sdc16 637+ 644 8- 64228+ 83 Linux > /dev/sdc17 645+ 646 2- 16033+ 83 Linux > /dev/sdc18 647+ 654 8- 64228+ 83 Linux > /dev/sdc19 655+ 656 2- 16033+ 83 Linux > /dev/sdc20 657+ 773 117- 939771 83 Linux > /dev/sdc21 774+ 789 16- 128488+ 83 Linux > /dev/sdc22 790+ 880 91- 730926 83 Linux > /dev/sdc23 881+ 1533 653- 5245191 83 Linux > /dev/sdc24 1795 1825 31 249007+ 83 Linux I have to ask: What are all those partitions? > # mount /dev/sdc22 /4free > mount: /dev/sdc22 is not a valid block device > > # ll /dev/sdc* > brw-rw---- 1 root disk 8, 32 Dec 1 2001 /dev/sdc > brw-rw---- 1 root disk 8, 33 Dec 1 2001 /dev/sdc1 > brw-rw---- 1 root disk 8, 42 Dec 1 2001 /dev/sdc10 > brw-rw---- 1 root disk 8, 43 Dec 1 2001 /dev/sdc11 > brw-rw---- 1 root disk 8, 44 Dec 1 2001 /dev/sdc12 > brw-rw---- 1 root disk 8, 45 Dec 1 2001 /dev/sdc13 > brw-rw---- 1 root disk 8, 46 Dec 1 2001 /dev/sdc14 > brw-rw---- 1 root disk 8, 47 Dec 1 2001 /dev/sdc15 > brw-r--r-- 1 root root 8, 48 Feb 13 16:26 /dev/sdc16 > brw-r--r-- 1 root root 8, 49 Feb 13 16:26 /dev/sdc17 > brw-r--r-- 1 root root 8, 50 Feb 13 16:26 /dev/sdc18 > brw-r--r-- 1 root root 8, 51 Feb 13 16:27 /dev/sdc19 > brw-rw---- 1 root disk 8, 34 Dec 1 2001 /dev/sdc2 > brw-r--r-- 1 root root 8, 52 Feb 13 16:27 /dev/sdc20 > brw-r--r-- 1 root root 8, 53 Feb 13 16:27 /dev/sdc21 > brw-r--r-- 1 root root 8, 54 Feb 13 16:27 /dev/sdc22 > brw-r--r-- 1 root root 8, 55 Feb 13 16:27 /dev/sdc23 > brw-r--r-- 1 root root 8, 56 Feb 13 16:27 /dev/sdc24 > brw-rw---- 1 root disk 8, 35 Dec 1 2001 /dev/sdc3 > brw-rw---- 1 root disk 8, 36 Dec 1 2001 /dev/sdc4 > brw-rw---- 1 root disk 8, 37 Dec 1 2001 /dev/sdc5 > brw-rw---- 1 root disk 8, 38 Dec 1 2001 /dev/sdc6 > brw-rw---- 1 root disk 8, 39 Dec 1 2001 /dev/sdc7 > brw-rw---- 1 root disk 8, 40 Dec 1 2001 /dev/sdc8 > brw-rw---- 1 root disk 8, 41 Dec 1 2001 /dev/sdc9 Hmm, using udev? Any chance udev incorrectly doesn't check for going past the end of the block devices allowed (each scsi device has 16 minors assigned, which gives you 15 partitions per device). Last device for sdc is 8,47. 8,48 (your sdc16) is actually sdd. > # dmesg > [snip] > scsi3 : ata_piix > ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA > ata1.00: ata1: dev 0 multi count 16 > ata1.00: configured for UDMA/33 > scsi4 : ata_piix > ata2.01: ATAPI, max MWDMA1 > ata2.01: configured for MWDMA1 > scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5 > SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB) > sdc: Write Protect is off > sdc: Mode Sense: 00 3a 00 00 > SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB) > sdc: Write Protect is off > sdc: Mode Sense: 00 3a 00 00 > SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 > sdc15 > > sd 3:0:0:0: Attached scsi disk sdc > sd 3:0:0:0: Attached scsi generic sg2 type 0 > [snip] > > I will try to have a look later. At least there it realized sdc15 is the last one by the looks of it. -- Len Sorensen - 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/
Powered by blists - more mailing lists