mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Giovanni Santini <giovannisantini93@yahoo.it>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	stable@vger.kernel.org
Cc: ntfs3@lists.linux.dev, almaz.alexandrovich@paragon-software.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Segfault running a binary in a compressed folder
Date: Tue, 11 Jun 2024 12:55:44 +0200	[thread overview]
Message-ID: <bed7da51-cf89-422d-84f7-cb3d89ffbe40@yahoo.it> (raw)
In-Reply-To: <0936a091-7a3a-40d7-8b87-837aed43966b@leemhuis.info>

Hi Thorsten, nice to chat again!
I am sorry for the lack of information, this is my second bug report to 
the kernel; the first one was via Bugzilla and I filled more information.

Now, the missing information is:

OS: ArchLinux

Tested kernels: both latest Linux stable (6.9.3) and mainline (6.10rc3)

Regression: no, I believe that this issue has been present forever.
I realized it may have been compression-related only recently.
I do remember testing ntfs3 long ago and having the same issues with a 
Ruby vendoring folder.

Please let me know if you need more information!

Bests,

Giovanni

On 2024-06-11 12:04, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 11.06.24 11:19, Giovanni Santini wrote:
>> I am writing to report the issue mentioned in the subject.
>>
>> Essentially, when running an executable from a compressed folder in an
>> NTFS partition mounted via ntfs3 I get a segfault.
>>
>> The error line I get in dmesg is:
>>
>> ntfs3: nvme0n1p5: ino=c3754, "hello" mmap(write) compressed not supported
>>
>> I've attached a terminal script where I show my source, Makefile and how
>> the error appears.
> You CCed the regression and the stable list, but that looks odd, as you
> don't even mention which kernel version you used (or which worked).
> Could you clarify? And ideally state if mainline (e.g. 6.10-rc3) is
> affected as well, as the answer to the question "who is obliged to look
> into this" depends on it.
>
> Ciao, Thorsten

-- 
Giovanni Santini


  reply	other threads:[~2024-06-11 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <08d7de3c-d695-4b0c-aa5d-5b5c355007f8.ref@yahoo.it>
     [not found] ` <08d7de3c-d695-4b0c-aa5d-5b5c355007f8@yahoo.it>
2024-06-11 10:04   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-11 10:55     ` Giovanni Santini [this message]
2024-06-11 11:15       ` Linux regression tracking (Thorsten Leemhuis)
2024-06-19  7:54         ` 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=bed7da51-cf89-422d-84f7-cb3d89ffbe40@yahoo.it \
    --to=giovannisantini93@yahoo.it \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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

all inboxes | Powered by JetHome®