From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Vladimir Davydov
<vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH cgroup/for-3.13-fixes] cgroup: fix oops in cgroup init failure path
Date: Mon, 9 Dec 2013 17:10:46 +0800 [thread overview]
Message-ID: <52A58916.4070708@huawei.com> (raw)
In-Reply-To: <20131205211814.GA29598-9pTldWuhBndy/B6EtB590w@public.gmane.org>
On 2013/12/6 5:18, Tejun Heo wrote:
> Hello, Vladimir.
>
> Thanks a lot for the report and fix; however, I really wanna make sure
> that only online css's become visible, so I wrote up a different fix.
> Can you please test this one?
>
Oh, I spotted this bug when reviewing a bug fix months ago.
http://lkml.org/lkml/2013/9/2/135
but that bug fix didn't go into mainline and it still exists even after
the below fix.
This is your updated fix that fixes both bugs.
http://lkml.org/lkml/2013/9/3/502
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
<linux-kernel@vger.kernel.org>, <cgroups@vger.kernel.org>,
<devel@openvz.org>
Subject: Re: [PATCH cgroup/for-3.13-fixes] cgroup: fix oops in cgroup init failure path
Date: Mon, 9 Dec 2013 17:10:46 +0800 [thread overview]
Message-ID: <52A58916.4070708@huawei.com> (raw)
In-Reply-To: <20131205211814.GA29598@mtj.dyndns.org>
On 2013/12/6 5:18, Tejun Heo wrote:
> Hello, Vladimir.
>
> Thanks a lot for the report and fix; however, I really wanna make sure
> that only online css's become visible, so I wrote up a different fix.
> Can you please test this one?
>
Oh, I spotted this bug when reviewing a bug fix months ago.
http://lkml.org/lkml/2013/9/2/135
but that bug fix didn't go into mainline and it still exists even after
the below fix.
This is your updated fix that fixes both bugs.
http://lkml.org/lkml/2013/9/3/502
next prev parent reply other threads:[~2013-12-09 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 9:00 [PATCH] cgroup: fix bug on cgroup_create() fail path Vladimir Davydov
2013-12-05 9:00 ` Vladimir Davydov
2013-12-05 21:18 ` [PATCH cgroup/for-3.13-fixes] cgroup: fix oops in cgroup init failure path Tejun Heo
[not found] ` <20131205211814.GA29598-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-12-06 7:02 ` Vladimir Davydov
2013-12-06 7:02 ` Vladimir Davydov
[not found] ` <52A1766F.5090808-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-12-06 16:13 ` Tejun Heo
2013-12-06 16:13 ` Tejun Heo
[not found] ` <20131206161312.GC13373-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-12-06 16:25 ` Tejun Heo
2013-12-06 16:25 ` Tejun Heo
[not found] ` <20131206162503.GD13373-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-12-06 18:04 ` Vladimir Davydov
2013-12-06 18:04 ` Vladimir Davydov
2013-12-06 18:02 ` Vladimir Davydov
2013-12-06 18:02 ` Vladimir Davydov
2013-12-09 9:10 ` Li Zefan [this message]
2013-12-09 9:10 ` Li Zefan
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=52A58916.4070708@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vdavydov-bzQdu9zFT3WakBO8gow8eQ@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 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.