public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: joshk@triplehelix.org (Joshua Kwan)
To: sparclinux@vger.kernel.org
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [2.6] busybox EFAULT on sparc64
Date: Wed, 18 Aug 2004 16:55:28 -0700	[thread overview]
Message-ID: <20040818235528.GA8070@triplehelix.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

Here's an example of a strange phenomenon seen by me and more recently
Jeff Bailey...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264482

I'm not sure exactly what's happening here. Summary: passing static
memory to mount(2) returns Bad address, and starting klogd hangs on a
fork(2) call. A mount call will succeed if the memory is copied first
onto the heap. This is 2.6.8 without any SPARC-specific patches, built
for sparc64.

You can check this out at (misnomer)
http://people.debian.org/~joshk/2.4.27/kernel-image-2.6.8-sparc/kernel-image-2.6.8-1-sparc64_2.4.27-1_sparc.deb
for yourself.

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.

Could I get any idea of what is going on here? I'm CC:ing lkml because
this may be a general 2.6 bug that neither Jeff or I have encountered.

-- 
Joshua Kwan

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]

             reply	other threads:[~2004-08-18 23:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 23:55 Joshua Kwan [this message]
2004-08-19  0:04 ` [2.6] busybox EFAULT on sparc64 Joshua Kwan
2004-08-19  0:06 ` David S. Miller
2004-08-19  0:07 ` David S. Miller
2004-08-19  1:43 ` David S. Miller
2004-08-19  9:09   ` Joshua Kwan
2004-08-19 16:52 ` David S. Miller
2004-08-20  5:02   ` 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=20040818235528.GA8070@triplehelix.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox