From: Andy Polyakov <appro@fy.chalmers.se>
To: Jens Axboe <axboe@suse.de>
Cc: Markus Plail <linux-kernel@gitteundmarkus.de>,
linux-kernel@vger.kernel.org
Subject: Re: readcd with 2.5 kernels and ide-cd
Date: Thu, 29 May 2003 23:43:56 +0200 [thread overview]
Message-ID: <3ED67F1C.BE1918E4@fy.chalmers.se> (raw)
In-Reply-To: fa.cqhesj4.p2oeoc@ifi.uio.no
> > Is there work going on to get readcd working with 2.5 kernels and
> > ide-cd (without ide-scsi)?
> >
> > strace readcd dev=/dev/dvd f=/dev/null
> > ...
> > ioctl(4, SNDCTL_TMR_TIMEBASE, 0xbfffedd8) = -1 ENOTTY (Inappropriate ioctl for device)
> > ...
> > ioctl(3, 0x2285, 0xbfffef9c) = -1 ENOTTY (Inappropriate ioctl for device)
>
> Something _very_ fishy is going on there.
Nothing fishy, nothing at all... It's as simple as
driver/block/scsi_ioctl.c doesn't accepts requestes larger than 64KB,
while readcd asks for 256KB.
> 0x2285 is the SG_IO ioctl.
sg_io returns EINVAL (line 163), but driver/block/ioctl.c transforms it
to ENOTTY (see last 8 lines).
> First call to it completes, second one returns -ENOTTY. Looks very much
> like some kernel bug, see the SNDCTL_TMR_TIMEBASE ioctl returning
> -ENOTTY in-between.
SNDCTL_TMR_TIMEBASE is actually TCGETS, originates in stdio and is not
relevant.
> I've seen this before (this very bug), but haven't chased it down.
It's not a bug, but implementation deficiency. Cheers. A.
next parent reply other threads:[~2003-05-29 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hr5v5at.1e5iqab@ifi.uio.no>
[not found] ` <fa.cqhesj4.p2oeoc@ifi.uio.no>
2003-05-29 21:43 ` Andy Polyakov [this message]
2003-05-30 6:48 ` readcd with 2.5 kernels and ide-cd Jens Axboe
2003-05-30 0:11 Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 16:44 Markus Plail
2003-05-29 17:30 ` Jens Axboe
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=3ED67F1C.BE1918E4@fy.chalmers.se \
--to=appro@fy.chalmers.se \
--cc=axboe@suse.de \
--cc=linux-kernel@gitteundmarkus.de \
--cc=linux-kernel@vger.kernel.org \
/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