WARNING: CPU: 1 PID: 4940 at /build/buildd/linux-3.13.0/mm/truncate.c:652 pagecache_isize_extended+0xfd/0x110() in 3.13.0-43-generic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Medium
|
Stefan Bader | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Stefan Bader | ||
Utopic |
Invalid
|
Medium
|
Unassigned | ||
Vivid |
Invalid
|
Medium
|
Stefan Bader | ||
linux-lts-trusty (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Stefan Bader | ||
Trusty |
Invalid
|
Undecided
|
Unassigned | ||
Utopic |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi all,
I have updated my ubuntu 14.04 LTS server this morning. Until then I
am seeing a lot of errors like:
[ 4174.782378] WARNING: CPU: 1 PID: 4940 at
/build/
pagecache_
[ 4174.782381] Modules linked in: ctr ccm ipt_MASQUERADE iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
iptable_filter ip_tables x_tables bridge stp llc snd_hda_codec_hdmi
arc4 nvidia(POX) rtl8187 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm
snd_page_alloc mac80211 snd_seq_midi snd_seq_midi_event cfg80211
eeprom_93cx6 snd_rawmidi joydev snd_seq snd_seq_device kvm_amd
snd_timer kvm drm snd sp5100_tco amd64_edac_mod soundcore edac_core
edac_mce_amd i2c_piix4 k10temp mac_hid xfs lp parport libcrc32c
pata_acpi hid_logitech_dj usbhid hid pata_atiixp tg3 ptp pps_core ahci
libahci
[ 4174.782433] CPU: 1 PID: 4940 Comm: URL Classifier Tainted: P
W OX 3.13.0-43-generic #72-Ubuntu
[ 4174.782436] Hardware name: HP ProLiant MicroServer, BIOS O41 10/01/2013
[ 4174.782439] 0000000000000009 ffff88006a90bd70 ffffffff81720bf6
0000000000000000
[ 4174.782443] ffff88006a90bda8 ffffffff810677cd 0000000000001000
ffff88012e12f598
[ 4174.782447] 0000000000000000 0000000000000008 00000000000dd9d0
ffff88006a90bdb8
[ 4174.782451] Call Trace:
[ 4174.782459] [<ffffffff81720
[ 4174.782464] [<ffffffff81067
[ 4174.782467] [<ffffffff81067
[ 4174.782472] [<ffffffff8115d
[ 4174.782476] [<ffffffff8115e
[ 4174.782515] [<ffffffffa00ce
[ 4174.782540] [<ffffffffa00c3
[ 4174.782546] [<ffffffff811c0
[ 4174.782550] [<ffffffff811bb
[ 4174.782554] [<ffffffff811bc
[ 4174.782558] [<ffffffff81731
[ 4174.782561] ---[ end trace aeb446f67bc8e89e ]---
===
break-fix: 90a8020278c1598
tags: |
added: kernel-bug-break-fix removed: kerne-bug-break-fix |
Changed in linux (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Utopic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Vivid): | |
status: | In Progress → Invalid |
Changed in linux-lts-trusty (Ubuntu Trusty): | |
status: | New → Invalid |
Changed in linux-lts-trusty (Ubuntu Utopic): | |
status: | New → Invalid |
Changed in linux-lts-trusty (Ubuntu Vivid): | |
status: | New → Invalid |
Changed in linux-lts-trusty (Ubuntu Precise): | |
assignee: | nobody → Stefan Bader (smb) |
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Stefan Bader (smb) |
Changed in linux (Ubuntu Precise): | |
status: | New → Invalid |
Changed in linux-lts-trusty (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Trusty): | |
status: | Confirmed → Fix Committed |
Changed in linux-lts-trusty (Ubuntu Precise): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-trusty removed: verification-needed-trusty |
tags: | removed: kernel-bug-break-fix |
From an email conversation on our mailing list from Stefan Bader:
This looks to be introduced by:
vfs: fix data corruption when blocksize < pagesize for mmaped data bugs.launchpad. net/bugs/ 1393477 fafd071736a0846 b38510309c upstream.
BugLink: http://
commit 90a8020278c1598
and fixed by:
commit f55fefd1a5a339b 1bd08c120b93312 d6eb64a9fb
Author: Jan Kara <email address hidden>
Date: Thu Oct 30 10:35:00 2014 +1100
mm: Remove false WARN_ON from pagecache_ isize_extended( )
and:
Oh, and just for explanation: this is a warning which is wrong. But until it is
fixed up the only impact is the number of annoying messages in dmesg. The follow
up change from upstream just removes the warning, nothing else. And since it is
"only" a warning there is no other effect.