linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Assorted overlayfs fixes for 4.19-rc5
Date: Mon, 24 Sep 2018 10:56:32 +0200	[thread overview]
Message-ID: <CAJfpegvkb8fk-a6+9j2Hf+oSkKOxAFF7NOLNZomUP+D4YYcjWg@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxj5dLOT3U5feWRmbh-BO8Qup9S3Cr9t_2oD5AKAHsLYxg@mail.gmail.com>

On Mon, Sep 24, 2018 at 10:25 AM, Amir Goldstein <amir73il@gmail.com> wrote:
> On Tue, Sep 18, 2018 at 4:34 PM Amir Goldstein <amir73il@gmail.com> wrote:
>>
>> Miklos,
>>
>> Found one memory leak that needs a fix for stable and
>> two missing freeze protections in stacked f_ops.
>>
>> Last patch is not a bugfix, but it fixes a trap that we set
>> for developers back in v4.10 - and you happened to step into.
>>
>> The series passed xfstests -g quick with overlayfs over
>> xfs and ext4 and the usual unionmount testsuite torture.
>>
>> The memory leak was detected with tests overlay/051,053
>> after I enabled kmemleak on my test setup.
>>
>
> Miklos,
>
> Maybe not enough time has passed to justify a PING, but you know I get
> edgy towards the end of a release cycle, especially a weird release cycle as
> this one...

Thanks for the reminder.   Pushed to overlayfs-next and will ask Greg
to pull before -rc6.  If I forget, please remind again ;)

Thanks,
Miklos

      reply	other threads:[~2018-09-24 14:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 13:34 [PATCH 0/4] Assorted overlayfs fixes for 4.19-rc5 Amir Goldstein
2018-09-18 13:34 ` [PATCH 1/4] ovl: fix memory leak on unlink of indexed file Amir Goldstein
2018-09-18 13:59   ` Greg KH
2018-09-18 15:14     ` Amir Goldstein
2018-09-18 13:34 ` [PATCH 2/4] ovl: fix freeze protection bypass in ovl_write_iter() Amir Goldstein
2018-09-18 13:34 ` [PATCH 3/4] ovl: fix freeze protection bypass in ovl_clone_file_range() Amir Goldstein
2018-09-18 13:34 ` [PATCH 4/4] vfs: swap names of {do,vfs}_clone_file_range() Amir Goldstein
2018-09-24  8:25 ` [PATCH 0/4] Assorted overlayfs fixes for 4.19-rc5 Amir Goldstein
2018-09-24  8:56   ` Miklos Szeredi [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=CAJfpegvkb8fk-a6+9j2Hf+oSkKOxAFF7NOLNZomUP+D4YYcjWg@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.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).