Bug 1141593 - [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 [NEEDINFO]
Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fedora-kernel-xfs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e68bdf642f572e081f50a6fb57c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-15 01:31 UTC by Robert Sigler
Modified: 2014-12-10 14:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 14:58:51 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (185.06 KB, text/plain)
2014-09-15 01:31 UTC, Robert Sigler
no flags Details

Description Robert Sigler 2014-09-15 01:31:48 UTC
Description of problem:
SATA drives attached via USB 3 hub. Errors repeat on an interval.

Additional info:
reporter:       libreport-2.2.3
BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
IP: [<ffffffffa01d029f>] xfs_bmap_longest_free_extent+0x2f/0xa0 [xfs]
PGD 0 
Oops: 0000 [#1] SMP 
Modules linked in: tcp_lp dm_crypt raid1 bnep bluetooth rfkill fuse xt_CHECKSUM tun ip6t_rpfilter ip6t_REJECT pl2303 xt_addrtype ipt_MASQUERADE xt_conntrack dm_thin_pool dm_persistent_data dm_bio_prison loop ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw uas usb_storage joydev uvcvideo snd_usb_audio videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usbmidi_lib v4l2_common snd_rawmidi videodev media snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support vfat fat x86_pkg_temp_thermal coretemp kvm_intel snd_hda_intel snd_hda_controller snd_hda_codec kvm snd_hwdep snd_seq snd_seq_device crct10dif_pclmul crc32_pclmul crc32c_intel snd_pcm ghash_clmulni_intel e1000e microcode mei_me i2c_i801 mei lpc_ich ptp snd_timer mfd_core snd pps_core soundcore tpm_tis tpm i2c_hid nuvoton_cir rc_core dw_dmac i2c_designware_platform dw_dmac_core i2c_designware_core nfsd auth_rpcgss nfs_acl lockd sunrpc xfs libcrc32c i915 i2c_algo_bit drm_kms_helper drm i2c_core sdhci_acpi sdhci video mmc_core
CPU: 3 PID: 3008 Comm: Chrome_FileThre Not tainted 3.16.2-200.fc20.x86_64 #1
Hardware name:                  /D54250WYK, BIOS WYLPT10H.86A.0027.2014.0710.1904 07/10/2014
task: ffff88040834c520 ti: ffff880405afc000 task.ti: ffff880405afc000
RIP: 0010:[<ffffffffa01d029f>]  [<ffffffffa01d029f>] xfs_bmap_longest_free_extent+0x2f/0xa0 [xfs]
RSP: 0018:ffff880405aff720  EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000373abc RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000373abc RDI: ffff8803f8b45a20
RBP: ffff880405aff750 R08: 0000000000000001 R09: ffff8803d04e5da8
R10: 0000000000000000 R11: 0000000000000001 R12: ffff8803f8b45800
R13: ffff8800715ecbc8 R14: ffff880405aff7dc R15: 0000000000373abc
FS:  00007f39b3ab1700(0000) GS:ffff88041fb80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000010 CR3: 00000003e8283000 CR4: 00000000001407e0
Stack:
 ffff880405aff76c 0000000000373abc ffff880405aff7dc 0000000000373abc
 ffff8803f8b45800 ffff880405aff7e0 ffff880405aff7a0 ffffffffa01d04c1
 ffff880405aff908 00000000cec38060 00000000913da2d7 0000000000000000
Call Trace:
 [<ffffffffa01d04c1>] xfs_bmap_btalloc_nullfb+0x81/0xf0 [xfs]
 [<ffffffffa01d792f>] xfs_bmap_btalloc+0x35f/0x710 [xfs]
 [<ffffffffa01d0123>] ? xfs_bmap_search_multi_extents+0xb3/0x140 [xfs]
 [<ffffffffa01d7cee>] xfs_bmap_alloc+0xe/0x10 [xfs]
 [<ffffffffa01d879a>] xfs_bmapi_write+0x52a/0xab0 [xfs]
 [<ffffffffa01e30ca>] xfs_da_grow_inode_int+0xba/0x300 [xfs]
 [<ffffffffa01be39c>] ? xfs_icsb_modify_counters+0x9c/0x190 [xfs]
 [<ffffffffa01c3fc5>] ? kmem_free+0x35/0x40 [xfs]
 [<ffffffffa01e3356>] xfs_da_grow_inode+0x46/0xa0 [xfs]
 [<ffffffffa01cdff1>] xfs_attr_shortform_to_leaf+0xb1/0x2e0 [xfs]
 [<ffffffff811d6632>] ? kmem_cache_alloc+0x1c2/0x1f0
 [<ffffffffa01c40a7>] ? kmem_zone_alloc+0x77/0x100 [xfs]
 [<ffffffffa01c40a7>] ? kmem_zone_alloc+0x77/0x100 [xfs]
 [<ffffffffa01ca0ad>] xfs_attr_set+0x36d/0x450 [xfs]
 [<ffffffffa01c39b2>] xfs_xattr_set+0x42/0x70 [xfs]
 [<ffffffff812179e2>] generic_setxattr+0x62/0x80
 [<ffffffff81218243>] __vfs_setxattr_noperm+0x63/0x1b0
 [<ffffffff81218445>] vfs_setxattr+0xb5/0xc0
 [<ffffffff8121857e>] setxattr+0x12e/0x1c0
 [<ffffffff811fe632>] ? final_putname+0x22/0x50
 [<ffffffff811fe8d9>] ? putname+0x29/0x40
 [<ffffffff81204082>] ? user_path_at_empty+0x72/0xc0
 [<ffffffff811f5e88>] ? __sb_start_write+0x58/0x100
 [<ffffffff811f0803>] ? chmod_common+0xf3/0x140
 [<ffffffff81218867>] SyS_setxattr+0xb7/0x100
 [<ffffffff8170e329>] system_call_fastpath+0x16/0x1b
Code: 00 55 48 89 e5 41 57 41 89 f7 41 56 49 89 d6 41 55 49 89 fd 41 54 53 48 83 ec 08 4c 8b 67 38 48 89 4d d0 4c 89 e7 e8 f1 39 03 00 <80> 78 10 00 48 89 c3 75 20 4c 89 ee b9 01 00 00 00 44 89 fa 4c 
RIP  [<ffffffffa01d029f>] xfs_bmap_longest_free_extent+0x2f/0xa0 [xfs]
 RSP <ffff880405aff720>

Comment 1 Robert Sigler 2014-09-15 01:31:51 UTC
Created attachment 937401 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-11-13 15:58:31 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2014-12-10 14:58:51 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.