linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefan Li <lizefan@huawei.com>
To: Alexander Potapenko <glider@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>, Tejun Heo <tj@kernel.org>,
	<roman.penyaev@profitbricks.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>, <jweiner@fb.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: lib, fs, cgroup: WARNING in percpu_ref_kill_and_confirm
Date: Thu, 1 Jun 2017 09:07:31 +0800	[thread overview]
Message-ID: <592F68D3.9050005@huawei.com> (raw)
In-Reply-To: <CAG_fn=XXna4GT2VTqtO1VNy1g82e4CE3K-jHXoQv75JWXBJt0A@mail.gmail.com>

On 2017/5/31 22:08, Alexander Potapenko wrote:
> On Fri, Mar 24, 2017 at 4:18 AM, Zefan Li <lizefan@huawei.com> wrote:
>> On 2017/3/23 22:04, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> The following program triggers WARNING in percpu_ref_kill_and_confirm:
>>> https://gist.githubusercontent.com/dvyukov/bcfcef3d6b24b9fd841b88ee20c14d4b/raw/a54aeeb09ad1e0659b0ed87ef5efc4480ab2536f/gistfile1.txt
>>>
>>
>> The bug can be triggered immediately. I'll look into it. Thanks!
> Hi Zefan,
> 
> Have you had a chance to look into this bug?
> It's still reproducible for me with KMSAN.

But I already fixed it..

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bfb0b80db5f9dca5ac0a5fd0edb765ee555e5a8e
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9732adc5d6520238223df16630f1f8cad2269317

      reply	other threads:[~2017-06-01  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 14:04 lib, fs, cgroup: WARNING in percpu_ref_kill_and_confirm Dmitry Vyukov
2017-03-24  3:18 ` Zefan Li
2017-05-31 14:08   ` Alexander Potapenko
2017-06-01  1:07     ` Zefan Li [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=592F68D3.9050005@huawei.com \
    --to=lizefan@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=glider@google.com \
    --cc=jweiner@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roman.penyaev@profitbricks.com \
    --cc=syzkaller@googlegroups.com \
    --cc=tj@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).