From: Willy Tarreau <w@1wt.eu>
To: marcelo@kvack.org, davem@davemloft.net
Cc: matthew@wil.cx, linux-kernel@vger.kernel.org, stable@kernel.org
Subject: [PATCH-2.4] 2 oopses in ethtool
Date: Wed, 5 Jul 2006 22:47:06 +0200 [thread overview]
Message-ID: <20060705204706.GA254@1wt.eu> (raw)
Hi Marcelo,
I got an oops today with 2.4.33-rc2 when playing ethtool games on my TG3
NIC. It was caused by a typo in ethtool.c, and while fixing it, I discovered
a second one.
David, a quick check showed that 2.6.17.1 has the first one fixed but not
second one (ethtool_set_pauseparam), so you might want to merge it too.
Cheers,
Willy
From: Willy Tarreau <willy@wtap.(none)>
Date: Wed, 5 Jul 2006 22:34:52 +0200
Subject: [PATCH] ethtool: two oopses in ethtool_set_coalesce() and ethtool_set_pauseparam()
The function pointers which were checked were for their get_* counterparts.
Typically a copy-paste typo.
Signed-off-by: Willy Tarreau <w@1wt.eu>
---
net/core/ethtool.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
d249002f5f8141f98a4f625e7333bf3c49768575
diff --git a/net/core/ethtool.c b/net/core/ethtool.c
index e140eb3..89c1031 100644
--- a/net/core/ethtool.c
+++ b/net/core/ethtool.c
@@ -349,7 +349,7 @@ static int ethtool_set_coalesce(struct n
{
struct ethtool_coalesce coalesce;
- if (!dev->ethtool_ops->get_coalesce)
+ if (!dev->ethtool_ops->set_coalesce)
return -EOPNOTSUPP;
if (copy_from_user(&coalesce, useraddr, sizeof(coalesce)))
@@ -403,7 +403,7 @@ static int ethtool_set_pauseparam(struct
{
struct ethtool_pauseparam pauseparam;
- if (!dev->ethtool_ops->get_pauseparam)
+ if (!dev->ethtool_ops->set_pauseparam)
return -EOPNOTSUPP;
if (copy_from_user(&pauseparam, useraddr, sizeof(pauseparam)))
--
1.3.3
next reply other threads:[~2006-07-05 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 20:47 Willy Tarreau [this message]
2006-07-05 21:29 ` [PATCH-2.4] 2 oopses in ethtool Jeff Garzik
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=20060705204706.GA254@1wt.eu \
--to=w@1wt.eu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=matthew@wil.cx \
--cc=stable@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.