mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@suse.de>, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [patch 2.6.13-rc6] Fix kmem read on 32-bit archs
Date: Sun, 14 Aug 2005 09:24:02 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0508140921240.3553@g5.osdl.org> (raw)
In-Reply-To: <200508141214_MC3-1-A731-BBE9@compuserve.com>



On Sun, 14 Aug 2005, Chuck Ebbert wrote:
>
>   The first thing drivers/char/mem.c:read_kmem does is convert the
> loff_t it gets as the offset for reading into an unsigned int.  This
> patch makes the kmem driver's llseek operator do that up-front, so
> that fs/read_write.c:rw_verify_area doesn't return -EINVAL when
> we try to read from higher addresses.

Why would rw_verify_area() return -EINVAL? It does

        if (unlikely((pos < 0) || (loff_t) (pos + count) < 0))
                goto Einval;

but pos and "loff_t" is 64-bit, and if the thing is negative in 64 bits, 
then that thing really _should_ fail.

Yes, the thing needs to be opened with O_LARGEFILE and you need to use 
"llseek()" to seek into it, but once you do that, everything should be 
fine.

		Linus

  parent reply	other threads:[~2005-08-14 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 16:12 Chuck Ebbert
2005-08-14 16:22 ` Andi Kleen
2005-08-14 16:24 ` Linus Torvalds [this message]
2005-08-14 16:50 ` Linus Torvalds
2005-08-14 20:36 Chuck Ebbert
2005-08-15  1:16 ` Linus Torvalds

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=Pine.LNX.4.58.0508140921240.3553@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®