From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Andrei Vagin <avagin-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>,
dvyukov-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: cgroup: avoid attaching a cgroup root to two different superblocks
Date: Tue, 18 Apr 2017 15:39:27 +0900 [thread overview]
Message-ID: <20170418063927.GA3899@wtj.duckdns.org> (raw)
In-Reply-To: <58F49BE2.8080200-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Hello, Li.
On Mon, Apr 17, 2017 at 06:41:38PM +0800, Zefan Li wrote:
> Now I remember why it didn't check NULL pointer... Could you try the following fix?
> It also reverts my previous patch. I would appreciate if you run the full test suit,
> to make sure it won't break anything.
Can you please refresh the patch on top of cgroup/for-next which
already has the original patch reverted? Let's apply this one for
for-4.12 w/o -stable. The bug isn't too likely to trigger in the wild
and the fix is kinda subtle. If necessary, we can last ask Greg to
pick it up once we know that the patch is safe.
> PS: Tejun, I found recently I can no longer receive your emails. Don't know why...
Hah, no idea. I didn't change anything on my side - all emails are
sent through gmail.com.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-04-18 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 8:51 [PATCH] cgroup: avoid attaching a cgroup root to two different superblocks Zefan Li
[not found] ` <58E7532B.4030505-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-04-11 0:01 ` Tejun Heo
2017-04-14 23:27 ` Andrei Vagin
[not found] ` <20170414232737.GC20350-1ViLX0X+lBJGNQ1M2rI3KwRV3xvJKrda@public.gmane.org>
2017-04-14 23:32 ` Andrei Vagin
[not found] ` <20170414233233.GA8183-1ViLX0X+lBJGNQ1M2rI3KwRV3xvJKrda@public.gmane.org>
2017-04-17 10:41 ` Zefan Li
[not found] ` <58F49BE2.8080200-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-04-18 4:09 ` Andrei Vagin
2017-04-18 6:39 ` Tejun Heo [this message]
2017-04-16 15:24 ` Tejun Heo
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=20170418063927.GA3899@wtj.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=avagin-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dvyukov-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.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).