Bug 1390716

Summary:	osd crashes when "radosgw-admin bi list --max-entries=1" command runing
Product:	Red Hat Ceph Storage	Reporter:	Matt Benjamin (redhat) <mbenjamin>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	shylesh <shmohan>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	unspecified
Version:	2.1	CC:	cbodley, ceph-eng-bugs, edonnell, hnallurv, kbader, kdreyer, mbenjamin, owasserm, sweil, yehuda
Target Milestone:	rc
Target Release:	2.2
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.5-22.el7cp Ubuntu: ceph_10.2.5-15redhat1xenial	Doc Type:	Bug Fix
Doc Text:	.Listing bucket info data no longer causes the OSD daemon to terminate unexpectedly Due to invalid memory access in an object class operation, the `radosgw-admin bi list --max-entries=1` command in some cases caused the Ceph OSD daemon to terminate unexpectedly with a segmentation fault. This bug has been fixed, and listing bucket info data no longer causes the OSD daemon to crash.	Story Points:	---
Clone Of:
Clones:	1390717 (view as bug list)		Environment:
Last Closed:	2017-03-14 15:46:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1383917, 1390717, 1412948

Description Matt Benjamin (redhat) 2016-11-01 17:47:26 UTC

Description of problem:
OSD can be induced to crash when given apparently correct argument for "bi list" RGW op


How reproducible:
100%


Steps to Reproduce:
1.radosgw-admin bi list --max-entries=1

Actual results:
1. OSD segfault


Expected results:
get 1-entry bucket index list segment, if applicable

Comment 8 Ken Dreyer (Red Hat) 2017-01-25 03:00:32 UTC

Matt, would you please cherry-pick https://github.com/ceph/ceph/pull/11758 downstream?

Comment 26 errata-xmlrpc 2017-03-14 15:46:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0514.html