All of lore.kernel.org
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: staging:rtl8192u: Possible memory leak?
Date: Wed, 26 Sep 2018 13:52:29 -0400	[thread overview]
Message-ID: <13481.1537984349@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20180926155201.GA25719@xux707-tw>

On Wed, 26 Sep 2018 16:52:03 +0100, John Whitmore said:

> This might all be a mute point as I seem to remember someone saying
> that memory allocation never fails in Linux and this can only happen
> if the first two allocations work and the third fails.

If memory allocation never fails, it would be a moot point, not a mute point.

However, memory allocation can indeed fail, and often does.

And you are correct, there is a memory leak.  While looking at that, I found
another minor issue. Patch submitted.

      reply	other threads:[~2018-09-26 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 15:52 staging:rtl8192u: Possible memory leak? John Whitmore
2018-09-26 17:52 ` valdis.kletnieks at vt.edu [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=13481.1537984349@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@lists.kernelnewbies.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.