linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: Michal Nazarewicz <mina86@mina86.com>,
	Peter Stuge <peter@stuge.se>,
	ath9k-devel <ath9k-devel@venema.h4ckr.net>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] net: wireless: wcn36xx: fix potential NULL pointer dereference
Date: Fri, 6 Dec 2013 11:12:58 -0500	[thread overview]
Message-ID: <20131206161258.GC13285@tuxdriver.com> (raw)
In-Reply-To: <CAFSJ42YckTDO=UV=fWG9mmVXSBYep1x6xiHahzGDcrB4dy0oOQ@mail.gmail.com>

FWIW, I merged the earlier version.  Please send any changes as a
follow-up patch, probably against wireless-next.

John

On Thu, Dec 05, 2013 at 08:41:29AM +0000, Eugene Krasnikov wrote:
> > +               if (msg_ind)
> > +                       break;
> > +               /* FIXME: Do something smarter then just printing an error. */
> > +               wcn36xx_err("Run out of memory while handling SMD_EVENT (%d)\n",
> 
> I think code will look neater if error case will be handled in "else"
> statement something like:
> if (msg_ind) {
> ...
> } else {
> /*print message*/
> }
> /*unlock and break;*/
> 
> How about that?
> 
> 
> On Mon, Dec 2, 2013 at 1:09 PM, Michal Nazarewicz <mina86@mina86.com> wrote:
> >
> > If kmalloc fails wcn36xx_smd_rsp_process will attempt to dereference
> > a NULL pointer.  There might be a better error recovery then just
> > printing an error, but printing an error message is better then the
> > current behaviour.
> >
> > Signed-off-by: Michal Nazarewicz <mina86@mina86.com>
> > ---
> >  drivers/net/wireless/ath/wcn36xx/smd.c | 19 +++++++++++++------
> >  1 file changed, 13 insertions(+), 6 deletions(-)
> >
> > On Sun, Dec 01 2013, Peter Stuge wrote:
> >> Michal Nazarewicz wrote:
> >>> +                    wcn36xx_err("Run out of memory while hnadling SMD_EVENT (%d)\n",
> >>> +                                msg_header->msg_type);
> >>
> >> Typo hnadling.
> >
> > Fixed.
> >
> > diff --git a/drivers/net/wireless/ath/wcn36xx/smd.c b/drivers/net/wireless/ath/wcn36xx/smd.c
> > index de9eb2c..3663394 100644
> > --- a/drivers/net/wireless/ath/wcn36xx/smd.c
> > +++ b/drivers/net/wireless/ath/wcn36xx/smd.c
> > @@ -2041,13 +2041,20 @@ static void wcn36xx_smd_rsp_process(struct wcn36xx *wcn, void *buf, size_t len)
> >         case WCN36XX_HAL_DELETE_STA_CONTEXT_IND:
> >                 mutex_lock(&wcn->hal_ind_mutex);
> >                 msg_ind = kmalloc(sizeof(*msg_ind), GFP_KERNEL);
> > -               msg_ind->msg_len = len;
> > -               msg_ind->msg = kmalloc(len, GFP_KERNEL);
> > -               memcpy(msg_ind->msg, buf, len);
> > -               list_add_tail(&msg_ind->list, &wcn->hal_ind_queue);
> > -               queue_work(wcn->hal_ind_wq, &wcn->hal_ind_work);
> > -               wcn36xx_dbg(WCN36XX_DBG_HAL, "indication arrived\n");
> > +               if (msg_ind) {
> > +                       msg_ind->msg_len = len;
> > +                       msg_ind->msg = kmalloc(len, GFP_KERNEL);
> > +                       memcpy(msg_ind->msg, buf, len);
> > +                       list_add_tail(&msg_ind->list, &wcn->hal_ind_queue);
> > +                       queue_work(wcn->hal_ind_wq, &wcn->hal_ind_work);
> > +                       wcn36xx_dbg(WCN36XX_DBG_HAL, "indication arrived\n");
> > +               }
> >                 mutex_unlock(&wcn->hal_ind_mutex);
> > +               if (msg_ind)
> > +                       break;
> > +               /* FIXME: Do something smarter then just printing an error. */
> > +               wcn36xx_err("Run out of memory while handling SMD_EVENT (%d)\n",
> > +                           msg_header->msg_type);
> >                 break;
> >         default:
> >                 wcn36xx_err("SMD_EVENT (%d) not supported\n",
> > --
> > 1.8.4.1
> >
> > --
> > Best regards,                                         _     _
> > .o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
> > ..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
> > ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
> 
> 
> 
> -- 
> Best regards,
> Eugene
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-12-06 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 17:07 [PATCH] net: wireless: wcn36xx: fix potential NULL pointer dereference Michal Nazarewicz
2013-12-01  0:47 ` [ath9k-devel] " Peter Stuge
2013-12-02 13:09   ` [PATCHv2] " Michal Nazarewicz
2013-12-05  8:41     ` Eugene Krasnikov
2013-12-06 16:12       ` John W. Linville [this message]
2013-12-07 17:13       ` [PATCH] net: wirelesse: wcn36xx: pull allocation outside of critical section Michal Nazarewicz
2013-12-09  7:27         ` Eugene Krasnikov
2013-12-09 11:34           ` [PATCH] net: wirelesse: wcn36xx: check allocation and trim " Michal Nazarewicz
2013-12-11 15:52             ` John W. Linville
2013-12-11 16:43               ` [PATCH RESEND] net: wirelesse: wcn36xx: pull allocation outside of " Michal Nazarewicz

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=20131206161258.GC13285@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=k.eugene.e@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mina86@mina86.com \
    --cc=peter@stuge.se \
    /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).