linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Miklos Szeredi <mszeredi@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: Stefan Priebe <s.priebe@profihost.ag>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 2/3] fuse: ignore 'data' argument of mount(..., MS_REMOUNT)
Date: Thu, 16 Jul 2020 00:27:32 +0000	[thread overview]
Message-ID: <20200716002733.3ECE62075B@mail.kernel.org> (raw)
In-Reply-To: <20200710115805.4478-2-mszeredi@redhat.com>

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: c30da2e981a7 ("fuse: convert to use the new mount API").

The bot has tested the following trees: v5.7.8, v5.4.51.

v5.7.8: Build OK!
v5.4.51: Failed to apply! Possible dependencies:
    7f5d38141e309 ("new primitive: __fs_parse()")
    82995cc6c5ae4 ("libceph, rbd, ceph: convert to use the new mount API")
    d7167b149943e ("fs_parse: fold fs_parameter_desc/fs_parameter_spec")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

  reply	other threads:[~2020-07-16  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 11:58 [PATCH 1/3] fuse: use ->reconfigure() instead of ->remount_fs() Miklos Szeredi
2020-07-10 11:58 ` [PATCH 2/3] fuse: ignore 'data' argument of mount(..., MS_REMOUNT) Miklos Szeredi
2020-07-16  0:27   ` Sasha Levin [this message]
2020-07-20  9:14     ` Miklos Szeredi
2020-07-10 11:58 ` [PATCH 3/3] fuse: reject options on reconfigure via fsconfig(2) Miklos Szeredi

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=20200716002733.3ECE62075B@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=s.priebe@profihost.ag \
    /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).