Skip to contentSkip to conversation

Regression in v2.6.19-git18: Unable to write CD

DISCUSSION Larry Finger 2 participants 3 messages Dec 14, 2006

lore
Share & tools
lore
#0 lore raw

There is a regression in v2.6.19-rc18 that makes one unable to write CD's. In k3b, the drive status shows no devices. I used git bisect to find the bad commit is the following:

0e75f9063f5c55fb0b0b546a7c356f8ec186825e is first bad commit commit 0e75f9063f5c55fb0b0b546a7c356f8ec186825e

Author: Mike Christie <[email protected]>
Date:   Fri Dec 1 10:40:55 2006 +0100

[PATCH] block: support larger block pc requests

This patch modifies blk_rq_map/unmap_user() and the cdrom and scsi_ioctl.c users so that it supports requests larger than bio by chaining them together.

:040000 040000 e8ca778ffe67908f24bb7bdf2e7f2e86c64c9d73 cc8c200f9e4b690b6ead717ecb8ff3687a2b5179 M
block
:040000 040000 512435f7df5397c515a27a58b944f553697c6902 f7eab7589a5950dd589d44015f02973f717da8c2 M
drivers
:040000 040000 c589bd48a88bffabbaaffb83a64aa8d484797991 717277cb369c0cb46301115285421de087825843 M
fs
:040000 040000 5083595bd2ac0c60764ac8dfe627bec09726edb8 874a14cb29cfda0c1dfe7b05638ac8304b1bd423 M
include

Larry

#1 lore raw
Quoted 3 lines · Larry Finger

There is a regression in v2.6.19-rc18 that makes one unable to write CD's. In k3b, the drive status shows no devices. I used git bisect to find the bad commit is the following:

Try a newer snapshot, it was fixed a few days ago.

Signature · 1 line
Jens Axboe
#2 lore raw
Quoted 5 lines · Jens Axboe
Quoted 1 line · Larry Finger

There is a regression in v2.6.19-rc18 that makes one unable to write CD's. In k3b, the drive status shows no devices. I used git bisect to find the bad commit is the following:

Try a newer snapshot, it was fixed a few days ago.

-git19 or -git20 fixed the problem.

Thanks,

Larry