linux-kernel - Re: [PATCH] [RFC] seqcount: Add lockdep functionality to seqcount/seqlock structures

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: <20130910081156.GK26785@twins.programming.kicks-ass.net>
Date:	Tue, 10 Sep 2013 10:11:56 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] [RFC] seqcount: Add lockdep functionality to
 seqcount/seqlock structures

On Mon, Sep 09, 2013 at 09:42:46PM -0700, John Stultz wrote:
> +++ b/include/linux/lockdep.h
> @@ -510,6 +510,21 @@ static inline void print_irqtrace_events(struct task_struct *curr)
>  
>  #ifdef CONFIG_DEBUG_LOCK_ALLOC
>  # ifdef CONFIG_PROVE_LOCKING
> +#  define seqcount_acquire(l, s, t, i)		lock_acquire(l, s, t, 0, 2, NULL, i)
> +#  define seqcount_acquire_read(l, s, t, i)	lock_acquire(l, s, t, 2, 2, NULL, i)
> +# else
> +#  define seqcount_acquire(l, s, t, i)		lock_acquire(l, s, t, 0, 1, NULL, i)
> +#  define seqcount_acquire_read(l, s, t, i)	lock_acquire(l, s, t, 2, 1, NULL, i)
> +# endif
> +# define seqcount_release(l, n, i)		lock_release(l, n, i)
> +#else
> +# define seqcount_acquire(l, s, t, i)		do { } while (0)
> +# define seqcount_acquire_read(l, s, t, i)	do { } while (0)
> +# define seqcount_release(l, n, i)		do { } while (0)
> +#endif

Please look at a recent lockdep.h, this pattern changed a little.
--
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/