From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 00/12] fs/adfs: miscellaneous updates
Date: Tue, 4 Jun 2019 14:47:46 +0100 [thread overview]
Message-ID: <20190604134746.m7dzefl77ftn4ap2@shell.armlinux.org.uk> (raw)
Hi Al,
The following patch series brings some updates to ADFS:
- Ensure that there is no padding in the on-disc record structure and
pack it to ensure correct layout.
- Add helper to retrieve the disc record structure from the first sector
of the disc map.
- Add helper to get the filesystem size.
- Directly use format_version from the disc record structure rather than
storing it in our superblock structure.
- Clean up kernel message printing, use %pV to avoid temporary buffers,
printing fragment ids with six hex digits.
- Ensure superblock flags are always set correctly, even on remounts,
specifically the noatime and read-only flags.
- Only update superblock flags on remount if we are returning success.
- Fix a potential use-after-free bug while parsing the filesystem
block size.
- Limit idlen (length of a fragment identifier in the map) according to
the directory type - only big directories support idlen > 16.
- Add and use some helpers to deal with time stamps and file types.
fs/adfs/adfs.h | 70 ++++++++++++++++---------
fs/adfs/dir.c | 25 ++++-----
fs/adfs/dir_f.c | 38 ++++++--------
fs/adfs/dir_fplus.c | 21 ++++----
fs/adfs/inode.c | 12 ++---
fs/adfs/map.c | 15 ++----
fs/adfs/super.c | 121 +++++++++++++++++++++++++------------------
include/uapi/linux/adfs_fs.h | 6 +--
8 files changed, 164 insertions(+), 144 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
reply other threads:[~2019-06-04 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190604134746.m7dzefl77ftn4ap2@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).