From: Laurent Riffard <laurent.riffard@free.fr>
To: Peter Osterlund <petero2@telia.com>
Cc: Andrew Morton <akpm@osdl.org>, Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state
Date: Sun, 06 Feb 2005 13:53:27 +0100 [thread overview]
Message-ID: <42061347.4090301@free.fr> (raw)
In-Reply-To: <m37jlmp0dv.fsf@telia.com>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Le 06.02.2005 09:18, Peter Osterlund a écrit :
[snip]
>
> Anyway, the problem is that the add-struct-request-end_io-callback
> patch forgot to update pktcdvd.c. This patch fixes it. It should
> probably be merged into the add-struct-request-end_io-callback patch,
> because that patch already fixes up other struct request users.
>
> Signed-off-by: Peter Osterlund <petero2@telia.com>
> ---
>
> linux-petero/drivers/block/pktcdvd.c | 1 +
> 1 files changed, 1 insertion(+)
>
> diff -puN drivers/block/pktcdvd.c~pktcdvd-endio-fix drivers/block/pktcdvd.c
> --- linux/drivers/block/pktcdvd.c~pktcdvd-endio-fix 2005-02-06 08:59:16.000000000 +0100
> +++ linux-petero/drivers/block/pktcdvd.c 2005-02-06 09:01:22.000000000 +0100
> @@ -375,6 +375,7 @@ static int pkt_generic_packet(struct pkt
> rq->ref_count++;
> rq->flags |= REQ_NOMERGE;
> rq->waiting = &wait;
> + rq->end_io = blk_end_sync_rq;
> elv_add_request(q, rq, ELEVATOR_INSERT_BACK, 1);
> generic_unplug_device(q);
> wait_for_completion(&wait);
> _
>
Ok, this patch fixed the problem. I'm able to mount the CDRW and write some data.
Thank you.
--
laurent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2005-02-06 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 16:49 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state Laurent Riffard
2005-02-06 0:43 ` Peter Osterlund
2005-02-06 1:48 ` Peter Osterlund
2005-02-06 6:23 ` Andrew Morton
2005-02-06 8:18 ` Peter Osterlund
2005-02-06 12:53 ` Laurent Riffard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42061347.4090301@free.fr \
--to=laurent.riffard@free.fr \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox