From: Peter Zijlstra <peterz@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>,
Elena Reshetova <elena.reshetova@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] locking/refcount: add sparse annotations to dec-and-lock functions
Date: Mon, 6 Jan 2020 16:26:29 +0100 [thread overview]
Message-ID: <20200106152629.GU2810@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <201912301131.2C7C51E8C6@keescook>
On Mon, Dec 30, 2019 at 11:32:31AM -0800, Kees Cook wrote:
> Is there a meaningful proposal anywhere for sparse to DTRT here?
These are what I found going through my Sent folder and Google'ing the
resulting subjects:
https://markmail.org/message/4obybcgqscznnx63
https://markmail.org/message/pp4ofksgactvgjbd?q=inverted_lock
> If
> not, it seems best to use what you've proposed until sparse reaches the
> point of being able to do this on its own.
Or just leave the silly sparse warning, they're easy to ignore.
prev parent reply other threads:[~2020-01-06 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 15:29 [PATCH] locking/refcount: add sparse annotations to dec-and-lock functions Eric Biggers
2019-12-28 11:49 ` Peter Zijlstra
2019-12-28 20:15 ` Eric Biggers
2019-12-30 18:43 ` Kees Cook
2019-12-30 19:15 ` Eric Biggers
2019-12-30 19:32 ` Kees Cook
2019-12-30 23:38 ` Luc Van Oostenryck
2020-01-03 1:35 ` Linus Torvalds
2020-01-03 2:18 ` Luc Van Oostenryck
2020-01-03 12:55 ` Dan Carpenter
2020-01-06 15:41 ` Peter Zijlstra
2020-01-06 17:54 ` Luc Van Oostenryck
2020-01-07 9:29 ` Peter Zijlstra
2020-01-06 15:26 ` Peter Zijlstra [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=20200106152629.GU2810@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=ebiggers@kernel.org \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).