From: Omar Sandoval <osandov@osandov.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Christoph Hellwig <hch@lst.de>,
Prasad Joshi <prasadjoshi.linux@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: logfs: GPF in logfs_alloc_inode
Date: Sun, 20 Nov 2016 15:48:04 -0800 [thread overview]
Message-ID: <20161120234804.GA18505@vader> (raw)
In-Reply-To: <CAFLxGvyYrLWaME6QNDBLTxiqLA+OxtWJSxQPrTVuQ4rZNUunJA@mail.gmail.com>
On Sun, Nov 20, 2016 at 10:05:16PM +0100, Richard Weinberger wrote:
> On Sun, Nov 20, 2016 at 10:57 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> > On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov <dvyukov@google.com> wrote:
> >> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval <osandov@osandov.com> wrote:
> >>> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
> >>>> Hello,
> >>>>
> >>>> The following program triggers GPF in logfs_alloc_inode:
> >>>> https://gist.githubusercontent.com/dvyukov/64a2113e4cb484d9b7e0ef4ff8a522d0/raw/fffdfb8b781ec758563e08765a258da71e6ff2a1/gistfile1.txt
> >>>
> >>> That should be fixed by this patch:
> >>> http://marc.info/?l=linux-kernel&m=147359909329298&w=2 ;)
> >>
> >>
> >> Nice!
> >>
> >> When will it merged into mainline?
> >
> >
> > Yes, delivery to joern@logfs.org and logfs@logfs.org fails.
>
> Wasn't the plan to remove logfs?
Yes, that's the patch I linked to.
--
Omar
prev parent reply other threads:[~2016-11-20 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 10:09 logfs: GPF in logfs_alloc_inode Dmitry Vyukov
2016-11-18 18:45 ` Omar Sandoval
2016-11-18 18:54 ` Dmitry Vyukov
2016-11-20 9:57 ` Dmitry Vyukov
2016-11-20 21:05 ` Richard Weinberger
2016-11-20 23:48 ` Omar Sandoval [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=20161120234804.GA18505@vader \
--to=osandov@osandov.com \
--cc=dvyukov@google.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasadjoshi.linux@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.