Project

General

Profile

Actions

Bug #24557

closed

client: segmentation fault in handle_client_reply

Added by Patrick Donnelly almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Q/A
Tags:
Backport:
mimic
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
crash
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2018-06-18 14:21:37.826 7f83ea25c700  1 -- 172.21.15.161:0/184666151 <== mds.5 172.21.15.14:6818/3657651955 2281 ==== client_reply(???:6732 = 0 (0) Success) v1 ==== 692+0+0 (1439663840 0 0) 0x7f83e4005380 con 0x5574e2313ff0
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 insert_trace from 2018-06-18 14:21:37.762054 mds.5 is_target=1 is_dentry=0
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460  features 0x1ffddff8ffa4ffff
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 update_snap_trace len 48
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 update_snap_trace snaprealm(0x1 nref=1533 c=0 seq=1 parent=0x0 my_snaps=[] cached_snapc=1=[]) seq 1 <= 1 and same parent, SKIPPING
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460  hrm  is_target=1 is_dentry=0
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 add_update_cap issued pAsLsXsFs -> pAsLsXsFs from mds.5 on 0x60000000417.head(faked_ino=0 ref=4 ll_ref=2 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:21:18.716340 mtime=2018-06-18 14:21:36.157940 ctime=2018-06-18 14:21:36.157940 caps=pAsLsXsFs(5=pAsLsXsFs) parents=0x10000000067.head["d78"] 0x7f83d84941a0)
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 insert_readdir_results 1 readdir items, end=1, hash_order=1, readdir_start , last_hash 0, next_offset 2
2018-06-18 14:21:37.826 7f83ea25c700 10 client.4460 _readdir_drop_dirp_buffer 0x7f838023c410
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 update_inode_file_time 0x10000000080.head(faked_ino=0 ref=1 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:19:46.614937 caps=pAsXs(5=pAsXs) parents=0x1000000001c.head["d47"] 0x7f83d849b290) pAsXs ctime 2018-06-18 14:21:36.157940 mtime 2018-06-18 14:19:46.614937
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 add_update_cap issued pAsXs -> pAsLsXsFs from mds.5 on 0x10000000080.head(faked_ino=0 ref=1 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:21:36.157940 caps=pAsLsXsFs(5=pAsLsXsFs) parents=0x1000000001c.head["d47"] 0x7f83d849b290)
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460  clearing (I_COMPLETE|I_DIR_ORDERED) on 0x1000000001c.head(faked_ino=0 ref=4 ll_ref=2 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=0.000000 mtime=2018-06-18 14:20:39.519316 ctime=2018-06-18 14:20:39.519316 caps=pAsLsXs(0=pAsLsXs,5=pAsLsXs) COMPLETE parents=0x10000000012.head["d0"] 0x7f83d848d530)
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 put_inode on 0x10000000080.head(faked_ino=0 ref=2 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:21:36.157940 caps=pAsLsXsFs(5=pAsLsXsFs) 0x7f83d849b290)
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 put_inode on 0x10000000080.head(faked_ino=0 ref=1 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:21:36.157940 caps=pAsLsXsFs(5=pAsLsXsFs) 0x7f83d849b290)
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 remove_cap mds.5 on 0x10000000080.head(faked_ino=0 ref=0 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:21:36.157940 caps=pAsLsXsFs(5=pAsLsXsFs) 0x7f83d849b290)
2018-06-18 14:21:37.827 7f83ea25c700 10 client.4460 put_inode deleting 0x10000000080.head(faked_ino=0 ref=0 ll_ref=0 cap_refs={} open={} mode=40777 size=0/0 nlink=1 btime=2018-06-18 14:17:57.177371 mtime=2018-06-18 14:19:46.614937 ctime=2018-06-18 14:21:36.157940 caps=- 0x7f83d849b290)
2018-06-18 14:21:37.828 7f83ea25c700 -1 *** Caught signal (Segmentation fault) **
 in thread 7f83ea25c700 thread_name:ms_dispatch

 ceph version 14.0.0-583-g44db180 (44db1805f8b3d0f2ca39b5967dd715b93ad26b81) nautilus (dev)
 1: (()+0xfffb0) [0x5574e0506fb0]
 2: (()+0xf6d0) [0x7f83f93766d0]
 3: (Inode::get()+0x28) [0x5574e04f8da8]
 4: (Client::link(Dir*, std::string const&, Inode*, Dentry*)+0xc8) [0x5574e0480968]
 5: (Client::insert_readdir_results(MetaRequest*, MetaSession*, Inode*)+0xc2f) [0x5574e04bcb0f]
 6: (Client::insert_trace(MetaRequest*, MetaSession*)+0xd61) [0x5574e04be641]
 7: (Client::handle_client_reply(MClientReply*)+0x146) [0x5574e04beff6]
 8: (Client::ms_dispatch(Message*)+0x2ab) [0x5574e04c968b]
 9: (DispatchQueue::entry()+0xb7a) [0x7f83fb3ca0ea]
 10: (DispatchQueue::DispatchThread::entry()+0xd) [0x7f83fb46b14d]
 11: (()+0x7e25) [0x7f83f936ee25]
 12: (clone()+0x6d) [0x7f83f8249bad]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

From: /ceph/teuthology-archive/pdonnell-2018-06-18_13:13:15-multimds-wip-pdonnell-testing-20180615.150516-testing-basic-smithi/2677613/remote/smithi161/log/ceph-client.1.17509.log.gz


Related issues 1 (0 open1 closed)

Copied to CephFS - Backport #35841: mimic: client: segmentation fault in handle_client_replyResolvedPrashant DActions
Actions #1

Updated by Zheng Yan almost 6 years ago

  • Status changed from New to Fix Under Review
Actions #2

Updated by Patrick Donnelly almost 6 years ago

  • Assignee set to Zheng Yan
  • Backport changed from mimic,luminous to mimic

Problem only in mimic/master. Introduced by 4f2fa427f483a29df168053d0021ee35c1aa207d.

Actions #3

Updated by Patrick Donnelly over 5 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #35841: mimic: client: segmentation fault in handle_client_reply added
Actions #5

Updated by Nathan Cutler over 5 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF