Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Slow path warnings and errors in log files for each device when restoring reconnected paths. See below:
Nov 17 10:45:04 lppb100 kernel: WARNING: at fs/fs-writeback.c:967 __mark_inode_dirty+0x108/0x160() (Tainted: P ---------------- )
Nov 17 10:45:04 lppb100 kernel: Hardware name: PowerEdge 2950
Nov 17 10:45:04 lppb100 kernel: Modules linked in: emcpvlumd(P)(U) emcpxcrypt(P)(U) emcpdm(P)(U) emcpgpx(P)(U) emcpmpx(P)(U) emcp(P)(U) autofs4 sunrpc ipv6 dm_mirror dm_region_hash dm_log dcdbas serio_raw iTCO_wdt iTCO_vendor_support bnx2 i5k_amb hwmon i5000_edac edac_core sg shpchp ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif ata_generic pata_acpi ata_piix mptsas mptscsih mptbase scsi_transport_sas qla2xxx scsi_transport_fc scsi_tgt radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mod [last unloaded: emcpioc]
Nov 17 10:45:04 lppb100 kernel: Pid: 5420, comm: blkid Tainted: P ---------------- 2.6.32-71.el6.x86_64 #1
Nov 17 10:45:04 lppb100 kernel: Call Trace:
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8106b857>] warn_slowpath_common+0x87/0xc0
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8106b8aa>] warn_slowpath_null+0x1a/0x20
Nov 17 10:45:04 lppb100 kernel: [<ffffffff81195798>] __mark_inode_dirty+0x108/0x160
Nov 17 10:45:04 lppb100 kernel: [<ffffffff811862bd>] touch_atime+0x12d/0x170
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8110d337>] generic_file_aio_read+0x377/0x730
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8116c65a>] do_sync_read+0xfa/0x140
Nov 17 10:45:04 lppb100 kernel: [<ffffffff81091ca0>] ? autoremove_wake_function+0x0/0x40
Nov 17 10:45:04 lppb100 kernel: [<ffffffff81171b14>] ? cp_new_stat+0xe4/0x100
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8120bf4b>] ? selinux_file_permission+0xfb/0x150
Nov 17 10:45:04 lppb100 kernel: [<ffffffff811ff3b6>] ? security_file_permission+0x16/0x20
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8116d085>] vfs_read+0xb5/0x1a0
Nov 17 10:45:04 lppb100 kernel: [<ffffffff810d40a2>] ? audit_syscall_entry+0x272/0x2a0
Nov 17 10:45:04 lppb100 kernel: [<ffffffff8116d1c1>] sys_read+0x51/0x90
Nov 17 10:45:04 lppb100 kernel: [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Nov 17 10:45:04 lppb100 kernel: ---[ end trace 4ad69a6adaa8e7a9 ]---
Nov 17 10:45:04 lppb100 kernel: bdi-block not registered
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.0 (Santiago)
Linux lcle022.lss.emc.com 2.6.32-71.el6.x86_64 #1 SMP Wed Sep 1 01:33:01 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
This can be easily reproduced.
Steps to Reproduce:
Another way of producing this is:
# mknod devzero c 1 5; touch devzero
Nov 18 16:02:22 lppb100 kernel: WARNING: at fs/fs-writeback.c:967 __mark_inode_dirty+0x108/0x160() (Tainted: P W ---------------- )
Nov 18 16:02:22 lppb100 kernel: Hardware name: PowerEdge 2950
Nov 18 16:02:22 lppb100 kernel: Modules linked in: emcpvlumd(P)(U) emcpxcrypt(P)(U) emcpdm(P)(U) emcpmpx(P)(U) emcpgpx(P)(U) emcp(P)(U) nfs lockd fscache nfs_acl auth_rpcgss nls_utf8 autofs4 sunrpc ipv6 dm_mirror dm_region_hash dm_log dcdbas serio_raw iTCO_wdt iTCO_vendor_support bnx2 i5k_amb hwmon i5000_edac edac_core sg shpchp ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif ata_generic pata_acpi ata_piix mptsas mptscsih mptbase scsi_transport_sas qla2xxx scsi_transport_fc scsi_tgt radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mod [last unloaded: emcpioc]
Nov 18 16:02:22 lppb100 kernel: Pid: 4979, comm: touch Tainted: P W ---------------- 2.6.32-71.el6.x86_64 #1
Nov 18 16:02:22 lppb100 kernel: Call Trace:
Nov 18 16:02:22 lppb100 kernel: [<ffffffff8106b857>] warn_slowpath_common+0x87/0xc0
Nov 18 16:02:22 lppb100 kernel: [<ffffffff8106b8aa>] warn_slowpath_null+0x1a/0x20
Nov 18 16:02:22 lppb100 kernel: [<ffffffff81195798>] __mark_inode_dirty+0x108/0x160
Nov 18 16:02:22 lppb100 kernel: [<ffffffff811880bc>] inode_setattr+0x7c/0x170
Nov 18 16:02:22 lppb100 kernel: [<ffffffffa02559a6>] ext4_setattr+0x186/0x390 [ext4]
Nov 18 16:02:22 lppb100 kernel: [<ffffffff81188318>] notify_change+0x168/0x340
Nov 18 16:02:22 lppb100 kernel: [<ffffffff8119b64c>] utimes_common+0xdc/0x1b0
Nov 18 16:02:22 lppb100 kernel: [<ffffffff8119b7b9>] do_utimes+0x99/0xf0
Nov 18 16:02:22 lppb100 kernel: [<ffffffff810d40a2>] ? audit_syscall_entry+0x272/0x2a0
Nov 18 16:02:22 lppb100 kernel: [<ffffffff8119b912>] sys_utimensat+0x32/0x90
Nov 18 16:02:22 lppb100 kernel: [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Nov 18 16:02:22 lppb100 kernel: ---[ end trace 4ad69a6adaa8e7b0 ]---
Nov 18 16:02:22 lppb100 kernel: bdi-char/mem not registered
Actual results:
Expected results:
Additional info:
This is known bug that has been patched in kernel 2.6.37. Please see the following links for more details:
“When a new disk is being discovered, add_disk() first ties the bdev to gendisk
(via register_disk()->blkdev_get()) and only after that calls
bdi_register_bdev(). Because register_disk() also creates disk's kobject, it
can happen that userspace manages to open and modify the device's data (or
inode) before its BDI is properly initialized leading to a warning in
__mark_inode_dirty().”
https://bugzilla.kernel.org/show_bug.cgi?id=16312https://bugzilla.kernel.org/attachment.cgi?id=30282
Can we have the fix that is mentioned in the other bug?
Comment 5RHEL Program Management
2011-01-07 04:51:22 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
(In reply to comment #4)
> Can we have the fix that is mentioned in the other bug?
Yes, the fix will be in 6.1 Beta, available to you shortly. Please try to reproduce this issue there.
I will close this as a dup of Bug 607605, since the stack trace is the same.
*** This bug has been marked as a duplicate of bug 607605 ***