Bug 682209

Summary: WARNING: at fs/buffer.c:1159 mark_buffer_dirty+0x82/0xa0()
Product: Red Hat Enterprise Linux 6 Reporter: Red Hat Case Diagnostics <case-diagnostics>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: esandeen
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2074404921
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-04 17:28:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Red Hat Case Diagnostics 2011-03-04 13:13:59 UTC 
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-71.14.1.el6.x86_64
package: kernel
reason: WARNING: at fs/buffer.c:1159 mark_buffer_dirty+0x82/0xa0() (Not tainted)
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
time: 1297770283
uid: 0
backtrace: WARNING: at fs/buffer.c:1159 mark_buffer_dirty+0x82/0xa0() (Not tainted)
Hardware name: 3680B56
Modules linked in: vfat fat ext3 jbd nls_utf8 udf crc_itu_t sr_mod cdrom option usb_wwan usbserial usb_storage ppp_deflate zlib_deflate ppp_async crc_ccitt ppp_generic slhc tun fuse rfcomm sco bridge stp llc bnep l2cap autofs4 sunrpc cpufreq_ondemand acpi_cpufreq freq_table xt_physdev ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 sha256_generic aesni_intel cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mirror dm_region_hash dm_log kvm_intel kvm uinput thinkpad_acpi hwmon wmi sg uvcvideo videodev v4l2_compat_ioctl32 btusb bluetooth arc4 ecb iwlagn iwlcore mac80211 cfg80211 rfkill i2c_i801 iTCO_wdt iTCO_vendor_support snd_hda_codec_intelhdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc e1000e ext4 mbcache jbd2 sd_mod crc_t10dif ahci i915 drm_kms_helper drm i2c_algo_bit i2c_core video output dm_m
od [last unloaded: microcode]
Pid: 5856, comm: umount Not tainted 2.6.32-71.14.1.el6.x86_64 #1
Call Trace:
[<ffffffff8106b8f7>] warn_slowpath_common+0x87/0xc0
[<ffffffff8106b94a>] warn_slowpath_null+0x1a/0x20
[<ffffffff8119e132>] mark_buffer_dirty+0x82/0xa0
[<ffffffffa04a5ecd>] journal_update_superblock+0x8d/0xf0 [jbd]
[<ffffffffa04a44dc>] cleanup_journal_tail+0xcc/0x140 [jbd]
[<ffffffffa04a4b91>] log_do_checkpoint+0x431/0x510 [jbd]
[<ffffffff8105671b>] ? update_shares+0x2b/0x70
[<ffffffff81066e0e>] ? select_task_rq_fair+0x9ee/0xab0
[<ffffffff8105fb12>] ? enqueue_entity+0x122/0x320
[<ffffffff8105c7f6>] ? update_curr+0xe6/0x1e0
[<ffffffff81061c11>] ? dequeue_entity+0x1a1/0x1e0
[<ffffffff810566d0>] ? __dequeue_entity+0x30/0x50
[<ffffffff810117bc>] ? __switch_to+0x1ac/0x320
[<ffffffff81059db2>] ? finish_task_switch+0x42/0xd0
[<ffffffff814c9405>] ? thread_return+0x6bd/0x778
[<ffffffff81091df6>] ? autoremove_wake_function+0x16/0x40
[<ffffffff81050099>] ? __wake_up_common+0x59/0x90
[<ffffffffa04a6341>] journal_destroy+0x131/0x220 [jbd]
[<ffffffff81091de0>] ? autoremove_wake_function+0x0/0x40
[<ffffffffa0651f6b>] ext3_put_super+0x3b/0x280 [ext3]
[<ffffffff8116f416>] generic_shutdown_super+0x56/0xe0
[<ffffffff8116f4d1>] kill_block_super+0x31/0x50
[<ffffffff81170580>] deactivate_super+0x70/0x90
[<ffffffff8118bc1f>] mntput_no_expire+0xbf/0x110
[<ffffffff8118c04b>] sys_umount+0x7b/0x3a0
[<ffffffff814ce014>] ? do_page_fault+0x154/0x3a0
[<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Comment 1 Red Hat Case Diagnostics 2011-03-04 13:14:22 UTC 
Created attachment 482286 [details]
File: backtrace
Comment 4 Eric Sandeen 2011-03-04 17:28:45 UTC 
Looks like a dup of 591466.

If possible, please communicate to the reporter that this should be fixed in kernel-2.6.32-112.el6 and beyond.

*** This bug has been marked as a duplicate of bug 591466 ***