From: Thomas Gleixner <tglx@linutronix.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH] timerfd: Protect the might cancel mechanism proper
Date: Fri, 10 Feb 2017 11:51:31 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702101150400.4036@nanos> (raw)
In-Reply-To: <CACT4Y+Y73cgc7s=LrcAR7uLs=zaRMkUwKUH5n391YPY4EQvNWw@mail.gmail.com>
On Fri, 10 Feb 2017, Dmitry Vyukov wrote:
> On Fri, Feb 10, 2017 at 11:13 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > ctx->might_cancel and ctx->clist are always in sync with the new lock and
> > that's the only interesting thing. On destruction we don't look at clockid
> > or such, we only care about might_cancel.
> >
> > What is not guaranteed to be in sync is the timer expiry time and the
> > cancel stuff, if two threads operate on the same timerfd in
> > parallel. That's what I do not care about at all.
>
> Ack. Thanks for looking at it bearing with me. Then:
Thanks for asking the questions. It's always good if we need to think it
over again.
Thanks,
tglx
next prev parent reply other threads:[~2017-02-10 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 14:24 [PATCH] timerfd: Protect the might cancel mechanism proper Thomas Gleixner
2017-02-01 12:43 ` Dmitry Vyukov
2017-02-02 18:54 ` Thomas Gleixner
2017-02-02 19:04 ` Dmitry Vyukov
2017-02-10 10:13 ` Thomas Gleixner
2017-02-10 10:26 ` Dmitry Vyukov
2017-02-10 10:51 ` Thomas Gleixner [this message]
2017-02-10 10:19 ` [tip:timers/core] " tip-bot for Thomas Gleixner
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=alpine.DEB.2.20.1702101150400.4036@nanos \
--to=tglx@linutronix.de \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).