linux-kernel - Re: [PATCH 3/3] kref: Remove the memory barriers

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Dec 2011 18:32:58 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	gregkh@...e.de, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, ostrikov@...dia.com,
	adobriyan@...il.com, eric.dumazet@...il.com, mingo@...e.hu,
	Oliver Neukum <oneukum@...e.de>
Subject: Re: [PATCH 3/3] kref: Remove the memory barriers

On Mon, Dec 12, 2011 at 6:12 PM, Peter Zijlstra <peterz@...radead.org> wrote:

> I don't know the driver model, and I don't plan to start learning it
> now. But if what you said is possible its broken and no memory barriers
> will fix it.

IMO, you don't need to learn it, and my example is very simple and common
kref usage in device drivers, :-)

Could we only focus on it and see what is problem? and why won't memory
barrier fix it?

Anyway, device drivers are the most consumers of kref...

thanks,
-- 
Ming Lei
--
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/