From: Peter Zijlstra <peterz@infradead.org>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Michal Hocko <mhocko@suse.cz>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>, Paul Bunyan <pbunyan@redhat.com>
Subject: Re: [PATCH] watchdog: Fix race on single cpu boot
Date: Sat, 1 Aug 2015 18:25:22 +0200 [thread overview]
Message-ID: <20150801162522.GO2859@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <110159750.2156696.1438434352724.JavaMail.zimbra@redhat.com>
On Sat, Aug 01, 2015 at 09:05:52AM -0400, Ulrich Obergfell wrote:
>
> Don,
>
> > Uli privately has been working on a patchset that cleans up a bunch of these
> > race conditions. We believe it should cover this case. It uses the
> > proc_mutex to synchronize everything.
> >
> > I think he is reaching out to you. If you could try his patchset to see if
> > it fixes things, it might be a cleaner approach than what you are doing.
> >
> > <small time goes by>
> >
> > Ok, I was poked on IRC and you have already done this and it passed your
> > testcase. Let me get Uli to post his patches. :-)
> >
> > Cheers,
> > Don
>
> I posted the patch set here:
>
> https://lkml.org/lkml/2015/8/1/64
> https://lkml.org/lkml/2015/8/1/65
> https://lkml.org/lkml/2015/8/1/66
> https://lkml.org/lkml/2015/8/1/67
> https://lkml.org/lkml/2015/8/1/68
If only you didn't use lkml.org links, that site is flaky beyond
unusable.
Please use lkml.kernel.org/r/$msgid, that way people actually have a
chance of getting a working link and/or finding it in their local
archive.
next prev parent reply other threads:[~2015-08-01 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 11:56 [PATCH] watchdog: Fix race on single cpu boot Jiri Olsa
2015-07-31 15:36 ` Don Zickus
2015-08-01 13:05 ` Ulrich Obergfell
2015-08-01 16:25 ` Peter Zijlstra [this message]
2015-08-02 11:09 ` Ulrich Obergfell
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=20150801162522.GO2859@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@kernel.org \
--cc=pbunyan@redhat.com \
--cc=uobergfe@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.