From: "David S. Miller" <davem@redhat.com>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6] busybox EFAULT on sparc64
Date: Thu, 19 Aug 2004 00:06:00 +0000 [thread overview]
Message-ID: <20040818170600.035e2345.davem@redhat.com> (raw)
In-Reply-To: <20040818235528.GA8070@triplehelix.org>
On Wed, 18 Aug 2004 16:55:28 -0700
joshk@triplehelix.org (Joshua Kwan) wrote:
> I'm inclined to believe that the two bugs are related; these both happen
> with busybox-cvs and the exact same programs work with 2.4. Bastian
> Blank suggests that it is the compat wrapper for sys_mount that is not
> clean.
I think this analysis is faulty, all of the userspace accesses done
by the compat layer for sys_mount() are done exactly using the same
code the normal sys_mount() uses, namely copy_mount_options().
WARNING: multiple messages have this Message-ID (diff)
From: "David S. Miller" <davem@redhat.com>
To: joshk@triplehelix.org (Joshua Kwan)
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6] busybox EFAULT on sparc64
Date: Wed, 18 Aug 2004 17:06:00 -0700 [thread overview]
Message-ID: <20040818170600.035e2345.davem@redhat.com> (raw)
In-Reply-To: <20040818235528.GA8070@triplehelix.org>
On Wed, 18 Aug 2004 16:55:28 -0700
joshk@triplehelix.org (Joshua Kwan) wrote:
> I'm inclined to believe that the two bugs are related; these both happen
> with busybox-cvs and the exact same programs work with 2.4. Bastian
> Blank suggests that it is the compat wrapper for sys_mount that is not
> clean.
I think this analysis is faulty, all of the userspace accesses done
by the compat layer for sys_mount() are done exactly using the same
code the normal sys_mount() uses, namely copy_mount_options().
next prev parent reply other threads:[~2004-08-19 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 23:55 [2.6] busybox EFAULT on sparc64 Joshua Kwan
2004-08-18 23:55 ` Joshua Kwan
2004-08-19 0:04 ` Joshua Kwan
2004-08-19 0:04 ` Joshua Kwan
2004-08-19 0:06 ` David S. Miller [this message]
2004-08-19 0:06 ` David S. Miller
2004-08-19 0:07 ` David S. Miller
2004-08-19 0:07 ` David S. Miller
2004-08-19 1:43 ` David S. Miller
2004-08-19 1:43 ` David S. Miller
2004-08-19 9:09 ` Joshua Kwan
2004-08-19 9:09 ` Joshua Kwan
2004-08-19 16:52 ` David S. Miller
2004-08-19 16:52 ` David S. Miller
2004-08-20 5:02 ` David S. Miller
2004-08-20 5:02 ` David S. Miller
2004-08-27 0:57 ` Joshua Kwan
2004-08-27 1:06 ` David S. Miller
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=20040818170600.035e2345.davem@redhat.com \
--to=davem@redhat.com \
--cc=joshk@triplehelix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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.