From: khali@linux-fr.org (Jean Delvare)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] MAX1111: Fix Race condition causing NULL pointer exception
Date: Tue, 12 Jul 2011 09:36:06 +0200 [thread overview]
Message-ID: <20110712093606.5db834cb@endymion.delvare> (raw)
In-Reply-To: <1310421038-14823-1-git-send-email-morpheus.ibis@gmail.com>
On Mon, 11 Jul 2011 23:50:38 +0200, Pavel Herrmann wrote:
> spi_sync call uses its spi_message parameter to keep completion information,
> using a drvdata structure is not thread-safe, potentially causing one thread
> having pointers to memory on or above other threads stack. use mutex to
> prevent multiple access
Honestly, I have no idea what "causing one thread having pointers to
memory on or above other threads stack" means (nor why this would be
bad.)
Patch applied nevertheless, as it fixes an actual bug which should be
fixed ASAP. Thanks for your contribution.
--
Jean Delvare
next prev parent reply other threads:[~2011-07-12 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 21:50 [PATCH v3] MAX1111: Fix Race condition causing NULL pointer exception Pavel Herrmann
2011-07-12 7:36 ` Jean Delvare [this message]
2011-07-12 8:04 ` Pavel Herrmann
2011-07-12 8:22 ` [lm-sensors] " Mark Brown
2011-07-12 8:40 ` Jean Delvare
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=20110712093606.5db834cb@endymion.delvare \
--to=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox