Bug 2123747 - Kernel 5.19 issues trying to access exfat volumes
Summary: Kernel 5.19 issues trying to access exfat volumes
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-09-02 13:49 UTC by Silviu C.
Modified: 2023-05-25 17:13 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2023-05-25 17:13:05 UTC
Type: Bug

Attachments (Terms of Use)
output of journalctl -b -1 --no-hostname -k > dmesg.txt (98.85 KB, text/plain)
2022-09-02 13:49 UTC, Silviu C.
no flags Details
ouput of lsmod (7.19 KB, text/plain)
2022-09-02 13:50 UTC, Silviu C.
no flags Details

Description Silviu C. 2022-09-02 13:49:11 UTC
Created attachment 1909226 [details]
output of journalctl -b -1 --no-hostname -k > dmesg.txt

1. Please describe the problem:

Trying to unpack an archive to an exfat formated drive causes extremely high cpu usage, swap file increased usage but not RAM usage increase. The volume also appears as read-only...

2. What is the Version-Release number of the kernel:

Happens with releases: kernel-5.19.4-200 and kernel-5.19.6-200

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Works fine with: kernel-5.18.19-200

First seen on: kernel-5.19.4-200

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

1) download mozilla firefox as tarball from here:
2) boot any of the released 5.19 series kernel
3) try to unpack the archive to an exfat formatted drive.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

- did not test

6. Are you running any modules that not shipped with directly Fedora's kernel?:

- No. lsmod output attached

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Silviu C. 2022-09-02 13:50:02 UTC
Created attachment 1909227 [details]
ouput of lsmod

Comment 2 Silviu C. 2022-09-03 13:11:06 UTC
Adding link to relevant discussion on Arch forums:


Patch available here:

Comment 3 Ben Cotton 2023-04-25 17:52:23 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ludek Smid 2023-05-25 17:13:05 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.