From: Phillip Susi <psusi@cfl.rr.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: BUG: attempt to access beyond end of device
Date: Tue, 18 Dec 2007 16:47:55 -0500 [thread overview]
Message-ID: <4768400B.9090306@cfl.rr.com> (raw)
In-Reply-To: <4766BB17.10803@m3y3r.de>
Thomas Meyer wrote:
> Hi,
>
> is somebody actually working on this bug?
>
> http://bugzilla.kernel.org/show_bug.cgi?id=9370
>
> I don't want to be impolite, but it's now more than a month since the
> bug was opened.
>
> The bug still exists in v2.6.24-rc5-43-gda8cadb:
Have you tried simply removing the line mentioned in the bug report from
pktcdvd.c?
rq->cmd_type = REQ_TYPE_BLOCK_PC;
Maybe Jens can comment on if that would be correct since he is more
familiar with the code than I.
next prev parent reply other threads:[~2007-12-18 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 18:08 BUG: attempt to access beyond end of device Thomas Meyer
2007-12-18 21:47 ` Phillip Susi [this message]
2007-12-18 22:01 ` Phillip Susi
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=4768400B.9090306@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.