From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-ua0-f173.google.com ([209.85.217.173]:34258 "EHLO
        mail-ua0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751080AbdE3IUG (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Tue, 30 May 2017 04:20:06 -0400
Received: by mail-ua0-f173.google.com with SMTP id u10so47057480uaf.1
        for <linux-fsdevel@vger.kernel.org>; Tue, 30 May 2017 01:20:06 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <20170530062454.GC6365@ZenIV.linux.org.uk>
References: <CACT4Y+ZNiki1Xdpe_m-=Tk+7TpeZNnvV-tq=cNai=Xs7dr0rbw@mail.gmail.com>
 <CACT4Y+ZHgE2r9fGsDS_7CHsxa53yrsx0Zp0TBvH4oeqg24w5Yg@mail.gmail.com>
 <20170305155707.GI29622@ZenIV.linux.org.uk> <CACT4Y+b2mfMmm1evdWn7PHkNOe1xhwtxqtUB83oawNRQ1ZzbKA@mail.gmail.com>
 <20170305163301.GJ29622@ZenIV.linux.org.uk> <CACT4Y+bZC8joKP=_TWbf1QT0SS7HBXe=b-9KNgHxxPPLFZ+FYA@mail.gmail.com>
 <20170305191802.GK29622@ZenIV.linux.org.uk> <CACT4Y+byghFT+RVGoP9-osQYQfgujLmLGiFfBiR1oQ2Gfqf9TQ@mail.gmail.com>
 <CACT4Y+asas_4rnUTZSXA4VKvgoUcjx=aHUuDn6SKX_t4MreogQ@mail.gmail.com>
 <CACT4Y+ZtqDjAGAQ-0fy8Dzbwvikvcg7zCH9yn25Ow7Awh2g_YA@mail.gmail.com> <20170530062454.GC6365@ZenIV.linux.org.uk>
From: Dmitry Vyukov <dvyukov@google.com>
Date: Tue, 30 May 2017 10:19:45 +0200
Message-ID: <CACT4Y+YhaC3SFqdrhorJChC8TSnWD6anpwnLWe6ibEXbFQUEKg@mail.gmail.com>
Subject: Re: fs: use-after-free in path_lookupat
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        syzkaller <syzkaller@googlegroups.com>,
        Cong Wang <xiyou.wangcong@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Tue, May 30, 2017 at 8:24 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Mon, May 29, 2017 at 04:48:17PM +0200, Dmitry Vyukov wrote:
>
>> Al, do you want me to mail the patch?
>> I won't be able to write a super detailed description, but I can do
>> some format patch.
>
> It's been fixed by commit c0eb027e5aef7; if you are still able to
> trigger it on the current mainline, please yell - that would have
> to be something different.


Thanks for the update!

No, I can't say that I still see this. It happened very infrequently,
so I wanted to make sure that we don't lost it regardless of whether I
see it or not.