Ultralinux archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@gnu.org>
To: ultralinux@vger.kernel.org
Subject: [buytenh@gnu.org: [cry for advice] sparc64 bridging troubles]
Date: Thu, 10 Jan 2002 18:49:20 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-101068859405697@msgid-missing> (raw)

In the hope that people on this list will at least read this email until
the end before hitting reply and starting to rant..

Please CC on replies.  Thanks.


----- Forwarded message from Lennert Buytenhek <buytenh@gnu.org> -----

Date: Thu, 10 Jan 2002 11:59:25 -0500
From: Lennert Buytenhek <buytenh@gnu.org>
To: [unnamed sparc64 person]
Cc: narancs@narancs.tii.matav.hu
Subject: [cry for advice] sparc64 bridging troubles
User-Agent: Mutt/1.3.25i

Hi,

After hacking around the fact that the sparc64 PPP ioctl32 conversion
functions mess up the ifreq struct passed to _every_ SIOCDEVPRIVATE device
ioctl ever issued (since the numbers alias, yuck yuck fuck argh yuck), I'm
seeing a truly weird problem.

From net/bridge/br_device.c::br_dev_do_ioctl:

        data = (unsigned long *)rq->ifr_data;
==>    if (copy_from_user(args, data, 4*sizeof(unsigned long)))
                return -EFAULT;

This copy_from_user invocation hangs the box solid, every single time.  The
arguments it's called with are fffff8001395f910, 00000000effff9f8, 32.  I
would think these look OK (and even if they wouldn't I guess they shouldn't
hang the box).

Any good ideas?  The machine in question is (I think) a netra t1 200.  The
box itself is in Hungary, and I can't reboot it by myself, which makes it
inconvenient both for me and the CC'ed person to test things.


thanks,
Lennert

----- End forwarded message -----

             reply	other threads:[~2002-01-10 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 18:49 Lennert Buytenhek [this message]
2002-01-11  8:15 ` [buytenh@gnu.org: [cry for advice] sparc64 bridging troubles] David S. Miller
2002-01-16 17:46 ` Lennert Buytenhek
2002-01-16 17:54 ` David S. Miller
2002-01-16 17:57 ` Lennert Buytenhek

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=marc-linux-ultrasparc-101068859405697@msgid-missing \
    --to=buytenh@gnu.org \
    --cc=ultralinux@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