Bug 1887645 - [abrt] btrfs-progs: btrfs_stack_stripe_devid(): btrfs killed by SIGSEGV
Summary: [abrt] btrfs-progs: btrfs_stack_stripe_devid(): btrfs killed by SIGSEGV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: btrfs-progs
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Bacik
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7409b7fda6b3cc434311866e8b5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-13 04:08 UTC by Chris Murphy
Modified: 2020-12-01 01:12 UTC (History)
5 users (show)

Fixed In Version: btrfs-progs-5.9-1.fc33 btrfs-progs-5.9-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-17 01:35:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (20.27 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: core_backtrace (1.01 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: cpuinfo (2.08 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: dso_list (721 bytes, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: environ (1.80 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: exploitable (82 bytes, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: limits (1.29 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: maps (5.06 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: mountinfo (3.27 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: open_fds (173 bytes, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
File: proc_pid_status (1.29 KB, text/plain)
2020-10-13 04:08 UTC, Chris Murphy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github kdave btrfs-progs issues 303 0 None closed 'btrfs filesystem usage' crashes during device removal 2020-11-16 14:05:43 UTC

Description Chris Murphy 2020-10-13 04:08:38 UTC 
Description of problem:
Two device btrfs. Removal of one device is in progress. 'btrfs fi us' crashes.

Version-Release number of selected component:
btrfs-progs-5.7-5.fc33

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        btrfs fi us /mnt/fire
crash_function: btrfs_stack_stripe_devid
executable:     /usr/sbin/btrfs
journald_cursor: s=953955ae9b7945e1a0a5ae08d7ea2ba7;i=1cb4f;b=d736d84b45204680b9c743a058fdb08e;m=42b10b5bb;t=5b1858192ef9c;x=c620f5fb7caefb1e
kernel:         5.9.0-0.rc8.28.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 btrfs_stack_stripe_devid at ./ctree.h:1598
 #1 add_info_to_list at cmds/filesystem-usage.c:59
 #2 load_chunk_info at cmds/filesystem-usage.c:185
 #3 load_chunk_and_device_info at cmds/filesystem-usage.c:1126
 #4 cmd_filesystem_usage at cmds/filesystem-usage.c:1126
 #5 cmd_execute at cmds/commands.h:125
Comment 1 Chris Murphy 2020-10-13 04:08:41 UTC 
Created attachment 1721079 [details]
File: backtrace
Comment 2 Chris Murphy 2020-10-13 04:08:42 UTC 
Created attachment 1721080 [details]
File: core_backtrace
Comment 3 Chris Murphy 2020-10-13 04:08:43 UTC 
Created attachment 1721081 [details]
File: cpuinfo
Comment 4 Chris Murphy 2020-10-13 04:08:43 UTC 
Created attachment 1721082 [details]
File: dso_list
Comment 5 Chris Murphy 2020-10-13 04:08:44 UTC 
Created attachment 1721083 [details]
File: environ
Comment 6 Chris Murphy 2020-10-13 04:08:45 UTC 
Created attachment 1721084 [details]
File: exploitable
Comment 7 Chris Murphy 2020-10-13 04:08:46 UTC 
Created attachment 1721085 [details]
File: limits
Comment 8 Chris Murphy 2020-10-13 04:08:46 UTC 
Created attachment 1721086 [details]
File: maps
Comment 9 Chris Murphy 2020-10-13 04:08:47 UTC 
Created attachment 1721087 [details]
File: mountinfo
Comment 10 Chris Murphy 2020-10-13 04:08:48 UTC 
Created attachment 1721088 [details]
File: open_fds
Comment 11 Chris Murphy 2020-10-13 04:08:49 UTC 
Created attachment 1721089 [details]
File: proc_pid_status
Comment 12 Fedora Update System 2020-11-15 16:47:09 UTC 
FEDORA-2020-c4bf3a681b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4bf3a681b
Comment 13 Fedora Update System 2020-11-15 16:47:10 UTC 
FEDORA-2020-3596748fea has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3596748fea
Comment 14 Fedora Update System 2020-11-16 01:49:57 UTC 
FEDORA-2020-c4bf3a681b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c4bf3a681b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4bf3a681b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 15 Fedora Update System 2020-11-16 02:06:03 UTC 
FEDORA-2020-3596748fea has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3596748fea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3596748fea

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 16 Fedora Update System 2020-11-17 01:35:42 UTC 
FEDORA-2020-3596748fea has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 17 Fedora Update System 2020-12-01 01:12:43 UTC 
FEDORA-2020-c4bf3a681b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.