From: Joe Perches <joe@perches.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: gregkh@linuxfoundation.org, valentina.manea.m@gmail.com,
lisa@xenapiadmin.com, ben@decadent.org.uk,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: check return value of dev_skb_alloc
Date: Thu, 19 Jun 2014 14:25:33 -0700 [thread overview]
Message-ID: <1403213133.2753.20.camel@joe-AO725> (raw)
In-Reply-To: <1403206156-3702-1-git-send-email-xerofoify@gmail.com>
On Thu, 2014-06-19 at 15:29 -0400, Nicholas Krause wrote:
> diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
[]
> @@ -59,7 +58,8 @@ static bool fw_download_code(struct net_device *dev, u8 *code_virtual_address,
> bLastIniPkt = 1;
>
> }
> -
> + if (!skb)
> + return false;
> skb = dev_alloc_skb(frag_length + 4);
Nick.
You may have compiled this, but it's obvious you
haven't tested it.
Please stop sending patches until you can verify what
you're doing with the code.
Please train a few more of your neurons for coding.
It takes some time and some practice but please don't
practice on linux-kernel.
Use google to find some other suitable forums like
http://cboard.cprogramming.com/c-programming/
Back to your patch:
if (!skb)
return false;
must go _after_
skb = dev_alloc_skb(frag_length + 4);
next prev parent reply other threads:[~2014-06-19 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 19:29 Nicholas Krause
2014-06-19 21:25 ` Joe Perches [this message]
2014-06-20 16:31 ` Nick Krause
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 2:24 Nicholas Krause
2014-06-19 2:45 ` Greg KH
2014-06-19 4:14 ` Joe Perches
2014-06-19 5:29 ` Dan Carpenter
2014-06-19 18:41 ` Nick Krause
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=1403213133.2753.20.camel@joe-AO725 \
--to=joe@perches.com \
--cc=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.com \
--cc=valentina.manea.m@gmail.com \
--cc=xerofoify@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
all inboxes | Powered by JetHome®