From: craftfever@tutamail.com
To: Ntfs3 <ntfs3@lists.linux.dev>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Regressions <regressions@lists.linux.dev>
Cc: Almaz Alexandrovich <almaz.alexandrovich@paragon-software.com>
Subject: Re: [Bug] Memory allocation errors and system crashing due to buggy disk cache/inode allocations by ntfs3 kernel module.
Date: Sat, 4 Oct 2025 13:03:26 +0200 (CEST) [thread overview]
Message-ID: <Oait04j--F-9@tutamail.com> (raw)
In-Reply-To: <OaiQgS3--F-9@tutamail.com>
Oct 4, 2025, 11:55 by craftfever@tutamail.com:
> I'm expecting serious bug when writing large amount of files to NTFS hard drive, shortly after memory allocation errors and system crash occurs/ Firstly, I thought, than this is bug in linux kernel itself, somewhat disk cache allocation error, but when I tested same operations on ext4 drive or using NTFS-3G module, bug is not present.
>
To reproduce a bug, try cloning two big Git repositories to an external NTFS drive mounted with ntfs3 module.
next prev parent reply other threads:[~2025-10-04 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 8:55 [Bug] Memory allocation errors and system crashing due to buggy disk cache/inode allocations by ntfs3 kernel module craftfever
2025-10-04 11:03 ` craftfever [this message]
2025-10-04 11:12 ` Thorsten Leemhuis
2025-10-04 11:26 ` craftfever
2025-11-14 9:39 ` Konstantin Komarov
2025-11-19 10:57 ` craftfever
2025-11-19 15:11 ` Konstantin Komarov
2025-11-23 10:35 ` craftfever
2025-11-26 8:54 ` Konstantin Komarov
2025-11-26 11:09 ` craftfever
-- strict thread matches above, loose matches on Subject: below --
2025-10-06 10:30 craftfever
2025-10-24 10:25 ` Konstantin Komarov
2025-11-26 14:08 craftfever
2025-12-02 7:17 ` Konstantin Komarov
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=Oait04j--F-9@tutamail.com \
--to=craftfever@tutamail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.