From: Jarek Poplawski <jarkao2@gmail.com>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] 3c515: Write outside array bounds
Date: Wed, 29 Jul 2009 22:43:00 +0200 [thread overview]
Message-ID: <20090729204300.GC3058@ami.dom.local> (raw)
In-Reply-To: <4A705904.4020505@gmail.com>
On Wed, Jul 29, 2009 at 04:13:24PM +0200, Roel Kluin wrote:
> Op 26-07-09 23:16, Jarek Poplawski schreef:
> > Roel Kluin wrote, On 07/26/2009 12:35 AM:
> >
> >> if dev_alloc_skb() fails on the first iteration, a write to
> >> cp->rx_ring[-1] occurs.
> >>
> >> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> >> ---
> >> Please review: can we error return like this?
> >
> >
> > I doubt we can return here: there is a lot of cleaning missing.
> >
> > Jarek P.
> I took drivers/net/3c59x.c as an example
>
> Is this going in the right direction?
The direction is right but a long and winding road... I guess it's for
somebody with drivers knowhow. It seems most of the corkscrew_close()
might be needed, including del_timer(). So, since this -1 case looks
quite unlikely, it might be reasonable to only limit the most obvious
damage with 'if (i != 0)' before [i - 1] write, like David advised
in lmc case?
Cheers,
Jarek P.
>
> diff --git a/drivers/net/3c515.c b/drivers/net/3c515.c
> index 3e00fa8..e94867d 100644
> --- a/drivers/net/3c515.c
> +++ b/drivers/net/3c515.c
> @@ -827,7 +827,7 @@ static int corkscrew_open(struct net_device *dev)
> skb = dev_alloc_skb(PKT_BUF_SZ);
> vp->rx_skbuff[i] = skb;
> if (skb == NULL)
> - break; /* Bad news! */
> + goto error; /* Bad news! */
> skb->dev = dev; /* Mark as being used by this device. */
> skb_reserve(skb, 2); /* Align IP on 16 byte boundaries */
> vp->rx_ring[i].addr = isa_virt_to_bus(skb->data);
> @@ -864,6 +864,17 @@ static int corkscrew_open(struct net_device *dev)
> ioaddr + EL3_CMD);
>
> return 0;
> +error:
> + pr_emerg("%s: no memory for rx ring\n", dev->name);
> + int j;
> + for (j = 0; j < i; j++) {
> + if (vp->rx_skbuff[j]) {
> + dev_kfree_skb(vp->rx_skbuff[j]);
> + vp->rx_skbuff[j] = NULL;
> + }
> + }
> + free_irq(dev->irq, dev);
> + return -ENOMEM;
> }
>
> static void corkscrew_timer(unsigned long data)
next prev parent reply other threads:[~2009-07-29 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 22:35 [PATCH] 3c515: Write outside array bounds Roel Kluin
2009-07-26 21:16 ` Jarek Poplawski
2009-07-29 14:13 ` Roel Kluin
2009-07-29 20:43 ` Jarek Poplawski [this message]
2009-07-30 10:26 ` Roel Kluin
2009-07-30 20:28 ` David Miller
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=20090729204300.GC3058@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@gmail.com \
/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).