From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: stable@kernel.org, linux-wireless@vger.kernel.org,
bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH stable] b43: Fix possible NULL pointer dereference in DMA code
Date: Sat, 14 Jun 2008 20:40:19 -0400 [thread overview]
Message-ID: <20080615004018.GA1396@tuxdriver.com> (raw)
In-Reply-To: <200806142257.55946.mb@bu3sch.de>
On Sat, Jun 14, 2008 at 10:57:55PM +0200, Michael Buesch wrote:
> This fixes a possible NULL pointer dereference in an error path of the
> DMA allocation error checking code. In case the DMA allocation address is invalid,
> the dev pointer is dereferenced for unmapping of the buffer.
>
> This is a cut-down version of 3ab4b64c46784ed83f213bf4e1b51d9c55858600
> which is upstream in John Linville's wireless-testing.git tree.
...which will probably be 028118a5f09a9c807e6b43e2231efdff9f224c74
in linux-2.6.git
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-06-15 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 20:57 [PATCH stable] b43: Fix possible NULL pointer dereference in DMA code Michael Buesch
2008-06-15 0:40 ` John W. Linville [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=20080615004018.GA1396@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=stable@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 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.