Bug 1090673 - [abrt] WARNING: CPU: 3 PID: 711 at fs/inode.c:281 drop_nlink+0x3e/0x50() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 3 PID: 711 at fs/inode.c:281 drop_nlink+0x3e/0x50()
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: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:07875641196620145fee6642ac3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-23 22:34 UTC by franck.bailliet
Modified: 2014-12-10 14:59 UTC (History)
8 users (show)

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


Attachments (Terms of Use)
File: dmesg (66.31 KB, text/plain)
2014-04-23 22:34 UTC, franck.bailliet
no flags Details

Description franck.bailliet 2014-04-23 22:34:07 UTC
Additional info:
reporter:       libreport-2.2.1
WARNING: CPU: 3 PID: 711 at fs/inode.c:281 drop_nlink+0x3e/0x50()
Modules linked in: bnep bluetooth ip6t_rpfilter cfg80211 rfkill ip6t_REJECT xt_conntrack 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 snd_hda_codec_hdmi snd_hda_codec_realtek kvm_amd kvm snd_hda_intel joydev ppdev usblp snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm edac_core snd_page_alloc snd_timer snd soundcore edac_mce_amd serio_raw microcode k10temp shpchp parport_pc parport i2c_nforce2 asus_atk0110 acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc ata_generic pata_acpi radeon i2c_algo_bit drm_kms_helper
ttm drm pata_marvell i2c_core sata_nv forcedeth pata_amd
CPU: 3 PID: 711 Comm: chronyd Not tainted 3.13.9-200.fc20.x86_64 #1
Hardware name: System manufacturer System Product Name/M2N68-AM Plus, BIOS 1802    06/10/2010
0000000000000009 ffff8800b7b3fc30 ffffffff81687dac 0000000000000000
ffff8800b7b3fc68 ffffffff8106d4dd ffff88022c60c0b0 ffff880073e62c00
ffff88022c60c0b0 ffff8800b8824c20 ffff880036534720 ffff8800b7b3fc78
Call Trace:
[<ffffffff81687dac>] dump_stack+0x45/0x56
[<ffffffff8106d4dd>] warn_slowpath_common+0x7d/0xa0
[<ffffffff8106d5ba>] warn_slowpath_null+0x1a/0x20
[<ffffffff811d2d5e>] drop_nlink+0x3e/0x50
[<ffffffff81247a6b>] ext4_dec_count.isra.25+0x1b/0x30
[<ffffffff8124c0d7>] ext4_rename+0x397/0x9c0
[<ffffffff8168d6c2>] ? mutex_lock+0x12/0x2f
[<ffffffff811c708c>] vfs_rename+0x56c/0x5b0
[<ffffffff811c7354>] SYSC_renameat+0x284/0x3f0
[<ffffffff811bb351>] ? __sb_end_write+0x31/0x60
[<ffffffff81322060>] ? lockref_put_or_lock+0x50/0x80
[<ffffffff811ca4cb>] SyS_rename+0x1b/0x20
[<ffffffff81696d69>] system_call_fastpath+0x16/0x1b

Comment 1 franck.bailliet 2014-04-23 22:34:12 UTC
Created attachment 889109 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-11-13 15:59:05 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:59:11 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.