From: Eric Sandeen <sandeen@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: brauner@kernel.org
Subject: Re: [PATCH 0/3] adfs, affs, befs: convert to new mount api
Date: Fri, 6 Sep 2024 10:56:22 -0500 [thread overview]
Message-ID: <8f83df83-5421-4141-9af3-1cd9a1e90372@redhat.com> (raw)
In-Reply-To: <20240829194138.2073709-1-sandeen@redhat.com>
On 8/29/24 2:39 PM, Eric Sandeen wrote:
> I'm going alphabetically for now ;)
>
> These were all tested against images I created or obtained, using a
> script to test random combinations of valid and invalid mount and
> remount options, and comparing the results before and after the changes.
>
> AFAICT, all parsing works as expected and behavior is unchanged.
>
> Thanks,
> -Eric
>
Hm, hold off on these. Found at least 1 string memory leak, will
resend along with hfs & hfsplus ... Sorry about that, didn't think
to check kmemleak before sending.
-Eric
prev parent reply other threads:[~2024-09-06 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 19:39 [PATCH 0/3] adfs, affs, befs: convert to new mount api Eric Sandeen
2024-08-29 19:39 ` [PATCH 1/3] adfs: convert adfs to use the " Eric Sandeen
2024-08-29 19:40 ` [PATCH 2/3] affs: convert affs " Eric Sandeen
2024-08-29 19:40 ` [PATCH 3/3] befs: convert befs " Eric Sandeen
2024-09-06 15:56 ` Eric Sandeen [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=8f83df83-5421-4141-9af3-1cd9a1e90372@redhat.com \
--to=sandeen@redhat.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@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).