From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: convert to use the new mount API
Date: Thu, 25 Apr 2024 17:58:42 +0900 [thread overview]
Message-ID: <CAKFNMo=2i6C2pUcvSuSuYFbkwnRxVKE3WnfjXTYTBRWXJ1MZtg@mail.gmail.com> (raw)
In-Reply-To: <20240424182716.6024-1-konishi.ryusuke@gmail.com>
On Thu, Apr 25, 2024 at 3:27 AM Ryusuke Konishi wrote:
>
> From: Eric Sandeen <sandeen@redhat.com>
>
> Convert nilfs2 to use the new mount API.
>
> [konishi.ryusuke: fixed missing SB_RDONLY flag repair in nilfs_reconfigure]
> Link: https://lkml.kernel.org/r/33d078a7-9072-4d8e-a3a9-dec23d4191da@redhat.com
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> ---
> Hi Andrew, please add this to the queue for the next merge window.
>
> As the title suggests, this patch transforms the implementation around
> nilfs2 mount/remount, so I reviewed all changes and tested all mount
> options and nilfs2-specific mount patterns (such as simultaneous
> mounting of snapshots and current tree). This one passed those checks.
>
> Thanks,
> Ryusuke Konishi
Hi Andrew, please once drop this patch from the -mm tree.
I found one bug causing a kernel bug in additional fault injection
testing, and also received issue reports from the 0-DAY CI Kernel Test
Service.
I will fix these issues and resend you a revised patch.
Thanks,
Ryusuke Konishi
next prev parent reply other threads:[~2024-04-25 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 18:27 [PATCH] nilfs2: convert to use the new mount API Ryusuke Konishi
2024-04-25 8:58 ` Ryusuke Konishi [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 22:12 Eric Sandeen
2024-04-04 20:11 ` Ryusuke Konishi
2024-04-04 20:35 ` Eric Sandeen
2024-04-04 22:33 ` Ryusuke Konishi
2024-04-05 1:21 ` Eric Sandeen
2024-04-05 1:46 ` Eric Sandeen
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='CAKFNMo=2i6C2pUcvSuSuYFbkwnRxVKE3WnfjXTYTBRWXJ1MZtg@mail.gmail.com' \
--to=konishi.ryusuke@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=sandeen@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).