linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH] ovl: fix wrong WARN_ON() in ovl_cache_update_ino()
Date: Fri, 24 Jan 2020 08:49:49 +0200	[thread overview]
Message-ID: <CAOQ4uxh3b1AEBEAax8OvXvyUXw5K9YJNo-tqvWuKdSpJVdYBRg@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegtcpqhiOqbdCCEz5_h=2WbYDWvLihAUYPC9KkB-uCmDbg@mail.gmail.com>

> I'm working this into the next batch bound for 5.6, unless something
> more urgent comes up before that.
>

overlayfs-next tested.
ovl-ino rebased.

You would probably want to squash the "merge conflict" below to overlayfs-next.

Thanks,
Amir.


--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -1348,7 +1348,7 @@ static int ovl_get_layers(struct super_block
*sb, struct ovl_fs *ofs,
         */
        err = get_anon_bdev(&ofs->fs[0].pseudo_dev);
        if (err) {
-               pr_err("overlayfs: failed to get anonymous bdev for
upper fs\n");
+               pr_err("failed to get anonymous bdev for upper fs\n");
                goto out;
        }

@@ -1409,7 +1409,7 @@ static int ovl_get_layers(struct super_block
*sb, struct ovl_fs *ofs,
         */
        if (ofs->numfs - !ofs->upper_mnt == 1) {
                if (ofs->config.xino == OVL_XINO_ON)
-                       pr_info("overlayfs: \"xino=on\" is useless
with all layers on same fs, ignore.\n");
+                       pr_info("\"xino=on\" is useless with all
layers on same fs, ignore.\n");
                ofs->xino_mode = 0;
        } else if (ofs->config.xino == OVL_XINO_ON && ofs->xino_mode < 0) {

      reply	other threads:[~2020-01-24  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23  6:40 [PATCH] ovl: fix wrong WARN_ON() in ovl_cache_update_ino() Amir Goldstein
2020-01-06  6:35 ` Amir Goldstein
2020-01-21 10:04   ` Amir Goldstein
2020-01-21 10:07     ` Miklos Szeredi
2020-01-24  6:49       ` Amir Goldstein [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=CAOQ4uxh3b1AEBEAax8OvXvyUXw5K9YJNo-tqvWuKdSpJVdYBRg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).