Bug #17547
closedceph-fuse 10.2.3 segfault
0%
Description
ceph-fuse 10.2.3 segfaults on 10.2.2 Ceph cluster.
ceph-fuse has #17275 and https://github.com/ceph/ceph/pull/10864 applied.
1: (()+0x29cbe7) [0x7f8a5b8eabe7] 2: (()+0xf8f0) [0x7f8a5a8fb8f0] 3: (Client::get_root_ino()+0x10) [0x7f8a5b7e0f80] 4: (CephFuse::Handle::make_fake_ino(inodeno_t, snapid_t)+0x18d) [0x7f8a5b7de79d] 5: (()+0x1910f1) [0x7f8a5b7df0f1] 6: (()+0x16405) [0x7f8a5b203405] 7: (()+0x16895) [0x7f8a5b203895] 8: (()+0x13394) [0x7f8a5b200394] 9: (()+0x80ca) [0x7f8a5a8f40ca] 10: (clone()+0x6d) [0x7f8a592588ad]
Files
Updated by John Spray over 7 years ago
ceph-fuse 10.2.3 segfaults on 10.2.2 Ceph cluster.
Are you asserting that it doesn't segfault on a 10.2.3 ceph cluster, or is it just coincidence that this issue occurred on a mixed-version system?
Updated by John Spray over 7 years ago
Seems likely to be same issue fixed by https://github.com/ceph/ceph/pull/10921 (i.e. duplicate of http://tracker.ceph.com/issues/17197)
Updated by Henrik Korkuc over 7 years ago
It is happening on 10.2.3 cluster too (just checked another cluster). It's just that I took this segfault from client which uses 10.2.2.
Updated by Henrik Korkuc over 7 years ago
I am preparing new build with a patch from https://github.com/ceph/ceph/pull/10921
Updated by John Spray over 7 years ago
Henrik: did that build fix the issue for you?
Updated by Henrik Korkuc over 7 years ago
looks good so far. I guess we can close this. Thanks!