Bug #20060
segmentation fault in _do_cap_update
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Correctness/Safety
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
7f1ec01c0700 -1 *** Caught signal (Segmentation fault ) ** in thread 7f1ec01c0700 thread_name:ms_dispatch ceph version 12.0.2-1513-g5921d98 (5921d98a0bde3b613153eda6afcb4ed89db02385) 1: (()+0x573a0f) [0x7f1ec6feaa0f] 2: (()+0x31c700f6d0) [0x7f1ec4b756d0] 3: (CInode::make_path_string(std::string&, bool, CDentry const*) const+0x5f) [0 x7f1ec6f0913f] 4: (CDir::get_path() const+0x3a) [0x7f1ec6ee460a] 5: (operator<<(std::ostream&, CDir const&)+0x31) [0x7f1ec6ee5c41] 6: (MDCache::create_subtree_map()+0xe72) [0x7f1ec6de4d72] 7: (MDLog::_submit_entry(LogEvent*, MDSLogContextBase*)+0x4e6) [0x7f1ec6f87a36] 8: (Locker::_do_cap_update(CInode*, Capability*, int, snapid_t, MClientCaps*, M ClientCaps*, bool*)+0x507) [0x7f1ec6e9d387] 9: (Locker::handle_client_caps(MClientCaps*)+0x1c6c) [0x7f1ec6ea083c] 10: (Locker::dispatch(Message*)+0xa5) [0x7f1ec6ea1715] 11: (MDSRank::handle_deferrable_message(Message*)+0xbb4) [0x7f1ec6d0ac04] 12: (MDSRank::_dispatch(Message*, bool)+0x1eb) [0x7f1ec6d177fb] 13: (MDSRankDispatcher::ms_dispatch(Message*)+0x15) [0x7f1ec6d18745] 14: (MDSDaemon::ms_dispatch(Message*)+0xf3) [0x7f1ec6d02433] 15: (DispatchQueue::entry()+0x7a2) [0x7f1ec726bc32] 16: (DispatchQueue::DispatchThread::entry()+0xd) [0x7f1ec70a24dd] 17: (()+0x31c7007ee5) [0x7f1ec4b6dee5] 18: (clone()+0x6d) [0x7f1ec3c5cd1d] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to int erpret this.
History
#1 Updated by Douglas Fuller almost 7 years ago
Full MDS log: https://www.dropbox.com/s/vfdqlqnyrjo4do6/mds.b.log.bz2
#2 Updated by Zheng Yan almost 7 years ago
please use gdb to which code triggered segfault
probably fixed by https://github.com/ceph/ceph/pull/15125/commits/22369f441865934074d1ccdd7923f1c4a37df002
#3 Updated by Douglas Fuller almost 7 years ago
- Status changed from New to Fix Under Review
Yes, seems to be.
#4 Updated by John Spray almost 7 years ago
- Status changed from Fix Under Review to Resolved