From: Jay Vosburgh <fubar@us.ibm.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Null pointer dereference in bonding driver, kernel 2.6.24
Date: Thu, 31 Jan 2008 14:55:29 -0800 [thread overview]
Message-ID: <3489.1201820129@death> (raw)
In-Reply-To: <47A24D65.2000001@redhat.com>
Chuck Ebbert <cebbert@redhat.com> wrote:
>In bond_main.c:
>
>int bond_create(char *name, struct bond_params *params, struct bonding **newbond)
>{
>...
> /* Check to see if the bond already exists. */
> list_for_each_entry_safe(bond, nxt, &bond_dev_list, bond_list)
> if (strnicmp(bond->dev->name, name, IFNAMSIZ) == 0) {
> printk(KERN_ERR DRV_NAME
> ": cannot add bond %s; it already exists\n",
>
>
>If 'name' is null we get a null dereference in strnicmp()
>
>The code was added in 2.6.24.
This is already fixed in netdev-2.6#upstream.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
prev parent reply other threads:[~2008-01-31 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 22:36 Null pointer dereference in bonding driver, kernel 2.6.24 Chuck Ebbert
2008-01-31 22:55 ` Jay Vosburgh [this message]
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=3489.1201820129@death \
--to=fubar@us.ibm.com \
--cc=cebbert@redhat.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;
as well as URLs for NNTP newsgroup(s).