On Thu, Oct 15, 2020 at 10:32:50AM -0700, Noah Meyerhans wrote: > The code around s3fs_open has changed quite a bit since the version in > buster was released.
Indeed there were many memory leak and similar fixes that can easily
lead to segfaults between 1.84 (in buster) and 1.87 (in bullseye)
> I'll work on testing a backport of the bullseye
> version on buster to test this.
If you'd like, I can provide you with a .deb of the backport, for easier
testing.
> Given the amount of code churn, I'm
> skeptical that we'll be able to isolate an easily backportable fix, but
> we'll see.
Indeed, and I'm not really _that_ interested in doing that work myself,
so if you see that 1.87 doesn't segfaults at most I'd probably upload
1.87 to buster-backports rather than figuring out the proper fix for the
"main" buster release. Unless somebody can isolate the fix :)
Probably going through the upstream git repository might help with that,
fwiw.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
