From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <OaiyHa1----9@tutamail.com>, <craftfever@tutamail.com>
Cc: <linux-kernel@vger.kernel.org>, <ntfs3@lists.linux.dev>,
<regressions@lists.linux.dev>, <regressions@leemhuis.info>
Subject: Re: [Bug] Memory allocation errors and system crashing due to buggy disk cache/inode allocations by ntfs3 kernel module.
Date: Fri, 24 Oct 2025 12:25:09 +0200 [thread overview]
Message-ID: <ca863643-e283-4a65-924d-2a5cacac134a@paragon-software.com> (raw)
In-Reply-To: <081a1c85c9891bd41fbbb2e0cbb702e696799d40@murena.io>
On 10/6/25 12:30, craftfever@murena.io wrote:
> (i'd to change e-mail for setting correspoing headers for reply)
> I made interesting investigation about the problem and found that if I put in kernel parameters preempt=full and threadirqs, crashing is gone, but corresponding process (git in this case) hangs and starting consuming CPU (therefore writing files is not happens) and it's impossible to kill it. But system is not crashing and stable in this case, case with full kernel preemption.
Hello,
Sorry for the delayed reply, and thanks for reporting this.
I'll try to reproduce the bug and follow up with my findings.
Regards,
Konstantin
next prev parent reply other threads:[~2025-10-24 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 10:30 craftfever
2025-10-24 10:25 ` Konstantin Komarov [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 14:08 craftfever
2025-12-02 7:17 ` Konstantin Komarov
2025-10-04 8:55 craftfever
2025-10-04 11:03 ` craftfever
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
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=ca863643-e283-4a65-924d-2a5cacac134a@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=OaiyHa1----9@tutamail.com \
--cc=craftfever@tutamail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=regressions@leemhuis.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome