From: k.lichtenwalder@computer.org
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 raw devices don't do 64bit offset?
Date: Tue, 17 Apr 2001 15:29:06 +0200 [thread overview]
Message-ID: <3ADC4522.A778AB4C@computer.org> (raw)
In-Reply-To: <E14p7Fo-0008VK-00@the-village.bc.nu> <3ADAEB38.44CBD71A@computer.org> <3ADB1243.327FB189@computer.org>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
Well, I looked a bit deeper into it. The limiting factor is the
s_maxbytes value from the superblock. (If the offset is larger than
s_maxbytes, default_llseek will return EINVAL, what I'm seeing), So,
where does it inherit this value from? My fs is reiserfs, so there's a
4GB limit. But the raw device is bound to the dvd (maj 22, min 64)?
Klaus
k.lichtenwalder@computer.org wrote:
>
> k.lichtenwalder@computer.org wrote:
> >
> > Alan Cox wrote:
> > >
> > > > sorry if this was already discussed, but I couldn't find it in the
> > > > archives. I'm trying to use xine (the linux dvd player) on
> > > > linux-2.4.3-ac3 and can't watch the whole dvd. The reason is that as
> > > > soon as the llseek sets a value in the offset_high field for sys_llseek,
> > > > I get a EINVAL back from the seek. Is this intentional? Or simply still
> > > > (only) a missing feature?
> > >
> > > Did you open the file with open64() ?
> >
> > No it's using open(), but sets -D_FILE_OFFSET_BITS=64. Looks like this
> > is not enough for the raw devices?
>
> Just to be on the right track I simply forced it to using open64 all
> along on this descriptor. It doesn't change anything. And, for the
> records, if I delete the raw device so that xine uses the block device,
> everything works fine.
--
------------------------------------------------------------------------
Klaus Lichtenwalder, Dipl. Inform., http://www.webforum.de/Klaus/
Fax +49-(0)89-91072699 Lichtenwalder@ACM.org
NIC: KL2100, KL76-RIPE K.Lichtenwalder@Computer.org
PGP Key fingerprint = 2658 EA97 E1A1 2680 5ECA 0036 80F5 F250 3CF8
C2C7
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2036 bytes --]
prev parent reply other threads:[~2001-04-17 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 8:52 2.4 raw devices don't do 64bit offset? k.lichtenwalder
2001-04-16 11:33 ` Alan Cox
2001-04-16 12:53 ` k.lichtenwalder
2001-04-16 15:39 ` k.lichtenwalder
2001-04-17 13:29 ` k.lichtenwalder [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=3ADC4522.A778AB4C@computer.org \
--to=k.lichtenwalder@computer.org \
--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 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.