From: Dmitry Vyukov <dvyukov@google.com>
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>
Subject: Re: fs: use-after-free in path_lookupat
Date: Tue, 30 May 2017 10:19:45 +0200 [thread overview]
Message-ID: <CACT4Y+YhaC3SFqdrhorJChC8TSnWD6anpwnLWe6ibEXbFQUEKg@mail.gmail.com> (raw)
In-Reply-To: <20170530062454.GC6365@ZenIV.linux.org.uk>
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.
prev parent reply other threads:[~2017-05-30 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 14:59 fs: use-after-free in path_lookupat Dmitry Vyukov
2017-03-04 19:39 ` Al Viro
2017-03-05 11:15 ` Dmitry Vyukov
2017-03-05 11:20 ` Dmitry Vyukov
2017-03-05 11:24 ` Dmitry Vyukov
2017-03-05 11:37 ` Dmitry Vyukov
2017-03-05 15:57 ` Al Viro
2017-03-05 16:14 ` Dmitry Vyukov
2017-03-05 16:33 ` Al Viro
2017-03-05 17:33 ` Dmitry Vyukov
2017-03-05 17:38 ` Dmitry Vyukov
2017-03-05 19:18 ` Al Viro
2017-03-06 9:46 ` Dmitry Vyukov
2017-03-23 14:17 ` Dmitry Vyukov
2017-04-28 6:19 ` Dmitry Vyukov
2017-05-29 14:48 ` Dmitry Vyukov
2017-05-30 6:24 ` Al Viro
2017-05-30 8:19 ` Dmitry Vyukov [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=CACT4Y+YhaC3SFqdrhorJChC8TSnWD6anpwnLWe6ibEXbFQUEKg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiyou.wangcong@gmail.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 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).