lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 11 Jun 2024 12:55:44 +0200
From: Giovanni Santini <giovannisantini93@...oo.it>
To: Linux regressions mailing list <regressions@...ts.linux.dev>,
 stable@...r.kernel.org
Cc: ntfs3@...ts.linux.dev, almaz.alexandrovich@...agon-software.com,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: Segfault running a binary in a compressed folder

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ