From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Fix double fetch in RCU version of hlist_*entry*
Date: Sun, 09 Nov 2014 12:34:43 +0800 [thread overview]
Message-ID: <3288757.dWnlOAcrMJ@diderot> (raw)
In-Reply-To: <1415052979-11108-1-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Monday 03 November 2014 23:16:19 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.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> compat.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Great find! Applied in revision 1e4a96a.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-09 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 22:16 [B.A.T.M.A.N.] [PATCH] batman-adv: Fix double fetch in RCU version of hlist_*entry* Sven Eckelmann
2014-11-09 4:34 ` Marek Lindner [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=3288757.dWnlOAcrMJ@diderot \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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