From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Alpha (EV56), lseek64, and /dev/kmem
Date: Sat, 04 Oct 2003 03:08:55 +0200 [thread overview]
Message-ID: <yw1x7k3lajx4.fsf@users.sourceforge.net> (raw)
In-Reply-To: 200310031942.50234.kelledin+LKML@skarpsey.dyndns.org
Kelledin <kelledin+LKML@skarpsey.dyndns.org> writes:
> I just found that on my Alpha box, lseek64() has a bit of
> difficulty seeking through /dev/kmem to extremely high
> values--specifically, any value >=0x8000000000000000 (the 64th
> bit set). Whenever it's supposed to seek to (and return) such a
> value, lseek64() returns -1 instead and sets errno to a
> seemingly random garbage value. Userspace has no real choice
> except to interpret this as an error.
>
> So far it's doing this on both xfs and ext2/3, so I'm betting
/dev/kmem hasn't anything to do with filesystems, right?
> it's fs-independent. I suppose it could be the kmem driver
> itself deciding to be quirky? I have no way of knowing if
> lseek64() will stumble like this on a real file, as I'd probably
> need more drive space than God to test that!
You could create a sparse file, but I don't think any filesystem
support that big files.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-10-04 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 0:42 [BUG] Alpha (EV56), lseek64, and /dev/kmem Kelledin
2003-10-04 1:08 ` Måns Rullgård [this message]
2003-10-04 1:36 ` Kelledin
2003-10-04 17:13 ` [PATCH] sysklogd: use up-to-date query_module() routine Kelledin
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=yw1x7k3lajx4.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--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