linux-kernel - [PATCH tip/core/urgent] Fix for hlist_entry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130314205307.GA27968@linux.vnet.ibm.com>
Date:	Thu, 14 Mar 2013 13:53:07 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	mingo@...e.hu
Cc:	linux-kernel@...r.kernel.org, davej@...hat.com,
	sasha.levin@...cle.com, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, caiqian@...hat.com,
	eric.dumazet@...il.com, lizefan@...wei.com
Subject: [PATCH tip/core/urgent] Fix for hlist_entry_safe() regression

Hello, Ingo

This series contains a single commit that fixes a regression in
hlist_entry_safe().  This macro references its argument twice, which
can cause NULL-pointer errors.  This commit applies a gcc statement
expression, creating a temporary variable to avoid the double reference.
This has been posted to LKML at https://lkml.org/lkml/2013/3/9/75.

Kudos to CAI Qian, whose testing uncovered this, to Eric Dumazet, who
spotted root cause, and to Li Zefan, who tested this commit.

This commit is available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent

							Thanx, Paul

----------------------------------------------------------------
Paul E. McKenney (1):
      list: Fix double fetch of pointer in hlist_entry_safe()

 include/linux/list.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/