Control: fixed -1 1.87-1
On Tue, Oct 20, 2020 at 05:28:21PM -0700, Noah Meyerhans wrote:
> Would you like me to go ahead and upload my backport to
> buster-backports? The debdiff against the bullseye version is trivial
> (see attached). Having it available in the archive would be helpful to
>
Would you like me to go ahead and upload my backport to
buster-backports? The debdiff against the bullseye version is trivial
(see attached). Having it available in the archive would be helpful to
me.
Thanks.
noah
diff -Nru s3fs-fuse-1.87/debian/changelog s3fs-fuse-1.87/debian/changelog
---
Control: notfound -1 1.87-1
After more than two days with no crashes in my 1.87 build, I think we
can pretty definitively say that the bug is fixed upstream.
On Fri, Oct 16, 2020 at 01:44:15PM +0200, Mattia Rizzolo wrote:
> > 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.
The backport was trivial to build, and I've been running
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)
>
The relevant stack trace seems to be
(gdb) bt
#0 tcache_get (tc_idx=19) at malloc.c:2934
#1 __GI___libc_malloc (bytes=328) at malloc.c:3042
#2 0x7f30c226cfd8 in operator new(unsigned long) () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x55fffc60472e in FdManager::Open
Package: s3fs
Version: 1.84-1
Severity: important
I'm not sure yet what's leading to the problem, but I have observed
multiple segfaults of s3fs on buster.
I am starting it with the following options:
s3fs -o uid=33 -o gid=33 -o allow_other -o default_permissions -o umask=0007 -o
iam_role=auto
7 matches
Mail list logo
