linux-kernel - Re: [PATCH] locking: type cleanup when accessing fast_read

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]

Message-ID: <20150520174251.GA6831@redhat.com>
Date:	Wed, 20 May 2015 19:42:51 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Nicholas Mc Guire <hofrat@...dl.org>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] locking: type cleanup when accessing fast_read_ctr

On 05/19, Peter Zijlstra wrote:
>
> So the value is unsigned by purpose; that said we should never cross the
> 2G I think, so it really doesn't matter much.

Yes, thanks, this is on purpose. Actually I was asked to make it "unsigned"
during the review, but I agree it looks better than "signed int" because
of overflows.

> That said; Oleg, should I post those patches implementing percpu-rwsem
> with the stuff we did for the hotplug lock a while back? I think I
> actually have those around somewhere.

Yes, this would be nice ;)

Oleg.

--
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/