From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Linux Netdev <linux-netdev@vger.kernel.org>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: dev_ifname32() fails on 32->64bit calls in copy_in_user().
Date: Wed, 31 Oct 2007 12:06:09 +1100 [thread overview]
Message-ID: <1193792769.9928.84.camel@pasglop> (raw)
In-Reply-To: <20071031003850.GE7517@tasint.org>
On Tue, 2007-10-30 at 17:38 -0700, Joel Becker wrote:
> Hello folks,
> I've been using a nice program on ppc32 with a ppc64
> system+kernel. It uses netlink to determine some network interface
> information. Recent kernels cause it to exit at the netlink stage. At
> first, I thought it was a bug in the program. Now I'm not so sure.
.../...
Reproduced here, I'll have a look, thanks.
Ben.
next prev parent reply other threads:[~2007-10-31 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 0:38 dev_ifname32() fails on 32->64bit calls in copy_in_user() Joel Becker
2007-10-31 1:06 ` Benjamin Herrenschmidt [this message]
2007-10-31 1:12 ` Arnd Bergmann
2007-10-31 2:35 ` Benjamin Herrenschmidt
2007-10-31 3:41 ` David Miller
2007-10-31 8:03 ` Eric W. Biederman
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=1193792769.9928.84.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Joel.Becker@oracle.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=linux-netdev@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