public inbox for backports@vger.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Sven Eckelmann <sven@narfation.org>, backports@vger.kernel.org
Subject: Re: [PATCH-resend] backports: Fix double fetch in hlist_for_each_entry*_rcu
Date: Sun, 16 Nov 2014 17:48:05 +0100	[thread overview]
Message-ID: <5468D545.1040807@hauke-m.de> (raw)
In-Reply-To: <1416078459-29315-1-git-send-email-sven@narfation.org>

On 11/15/2014 08:07 PM, Sven Eckelmann wrote:
> The backported (<3.9) version of hlist_for_each_entry_rcu and
> hlist_for_each_entry_safe uses the new macro hlist_entry_safe. It is called
> with an ACCESS_ONCE parameter for the first parameter ptr. This disallows
> merging of the two loads which the current version of the macro uses.
> 
> This is problematic because this macro must only generate one load. Otherwise
> with two contexts (or CPUs) following could happen:
> 
> 1. context 1 fetches the ptr to the last entry in hlist_entry_safe() and
>    accepts this non-NULL ptr
> 
> 2. context 2 deletes the last entry and terminates the list with NULL
> 
> 3. context 1 re-fetches the pointer, doesn't check for zero, calculates the
>    entry based on a NULL pointer
> 
> 4. context 1 crashes because it tries to load/write data from/to the invalid
>    address
> 
> Instead use a single load to a temporary variable and do the NULL-check and
> calculation based on that one. This is also the approach used in the current
> Linux versions and was introduced by Paul E. McKenney.
> 
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
>  backport/backport-include/linux/list.h | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
Thank you for your patch, it was pushed upstream.

Hauke

      reply	other threads:[~2014-11-16 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 19:07 [PATCH-resend] backports: Fix double fetch in hlist_for_each_entry*_rcu Sven Eckelmann
2014-11-16 16:48 ` Hauke Mehrtens [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=5468D545.1040807@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=backports@vger.kernel.org \
    --cc=sven@narfation.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