From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: Joel.Becker@oracle.com, netdev@vger.kernel.org,
Linux-Kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: dev_ifname32() fails on 32->64bit calls in copy_in_user().
Date: Tue, 30 Oct 2007 20:41:10 -0700 (PDT) [thread overview]
Message-ID: <20071030.204110.216540107.davem@davemloft.net> (raw)
In-Reply-To: <1193798124.9928.91.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Wed, 31 Oct 2007 13:35:24 +1100
> [PATCH] Fix new dev_ifname32 returning -EFAULT
>
> A stray semicolon slipped in the patch that updated dev_ifname32 to
> not be inline, causing it to always return -EFAULT. This fixes it.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Applied, thanks for the fix Ben!
next prev parent reply other threads:[~2007-10-31 3:41 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
2007-10-31 1:12 ` Arnd Bergmann
2007-10-31 2:35 ` Benjamin Herrenschmidt
2007-10-31 3:41 ` David Miller [this message]
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=20071030.204110.216540107.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Joel.Becker@oracle.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=benh@kernel.crashing.org \
--cc=ebiederm@xmission.com \
--cc=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