From: Roger Sewell <roger.sewell@cantab.net>
To: <linux-fsdevel@vger.kernel.org>
Subject: Crash using kmod-hfsplus on cp -a from one memory stick to another
Date: Sat, 27 Aug 2022 21:29:29 +0100 [thread overview]
Message-ID: <20220827212929.6089@revelation.broadband> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hello,
I understand that kmod-hfsplus is now no longer maintained, so that
reporting this is unlikely to get any attention; my motivation in
reporting it is to ensure that the existence of this bug is recorded
somewhere in case anybody looks at this module again.
Versions in use:
kernel.x86_64 5.14.0-70.17.1.el9_0 (rockylinux 9.0)
kmod-hfsplus.x86_64 0.4-1.el9 from elrepo
hfsplus-tools.x86_64 540.1.linux3-26.el9 from elrepo
How reproducible: always
Steps to produce:
1. Format a partition on each of two memory sticks with hfsplus using
mkfs.hfsplus;
2. Mount one of them on <mnt1> and the other on <mnt2>;
3. Populate <mnt1> with the contents of a standard rockylinux live
stick's hfsplus partition (partition 3 of such a stick) (although the
exact contents of the filesystem may not be important);
4. cp -a <mnt1>/* <mnt2>
Result: System crashes, leaving nothing in /var/log/messages.
Attached: kexec-dmesg.log and vmcore-dmesg.txt from the crash dump
(vmcore is too large).
Additional information: I've tried doing the same with vfat partitions
and the same problem does not occur. Nor does it occur if -r is
substituted for -a in the copy. Nor does it occur if copying is from
ext4 on disk to stick or vice versa.
I'm afraid that updating to later kernels and the like is beyond what I
have time (or expertise) to contribute - apologies.
Roger Sewell.
[-- Attachment #2: Part of crash dump --]
[-- Type: application/gzip, Size: 42761 bytes --]
reply other threads:[~2022-08-27 20:39 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=20220827212929.6089@revelation.broadband \
--to=roger.sewell@cantab.net \
--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).