Bug 854708 - EBUSY error when mapping FCoE target to iblock backend
Summary: EBUSY error when mapping FCoE target to iblock backend
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: 6.5
Assignee: Andy Grover
QA Contact: Bruno Goncalves
: 896409 (view as bug list)
Depends On: 903297 1030730
Blocks: 896413
TreeView+ depends on / blocked
Reported: 2012-09-05 15:54 UTC by Jason Mather
Modified: 2013-11-21 22:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-11-21 22:26:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Patch to replace blkdev_put with close_bdev_exclusive (530 bytes, application/octet-stream)
2012-09-05 15:54 UTC, Jason Mather
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1683 0 normal SHIPPED_LIVE fcoe-target-utils bug fix update 2013-11-20 21:52:32 UTC

Description Jason Mather 2012-09-05 15:54:49 UTC
Created attachment 610088 [details]
Patch to replace blkdev_put with close_bdev_exclusive

Description of problem:  Second mapping of block device to iblock backend fails with EBUSY because device is still claimed after being unmapped.

The initial mapping uses open_bdev_exclusive, but the unmap call uses blkdev_put instead of the correct call which is close_bdev_exclusive.

Version-Release number of selected component (if applicable): 2.6.32-279.5.2

How reproducible: Always

Steps to Reproduce:
1.  Create an iblock virtual device on a block device
2.  Delete the iblock virtual device
3.  Create the iblock virtual device again.
Actual results:
Fails with Device or resource busy

Expected results:

Additional info:
Patch attached.

Comment 2 Jason Mather 2012-09-14 13:47:38 UTC
This bug is not present in the upstream kernel.  It was introduced when the target code was backported which is why I'm reporting it here.

Comment 4 RHEL Program Management 2012-12-14 08:52:37 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Andy Grover 2013-02-27 00:35:26 UTC
*** Bug 896409 has been marked as a duplicate of this bug. ***

Comment 6 RHEL Program Management 2013-04-12 02:26:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

Comment 7 Bruno Goncalves 2013-08-07 10:41:26 UTC
Reproduced error on kernel-2.6.32-387.el6.x86_64

Fixed on kernel-2.6.32-407.el6.x86_64

Comment 9 Marcus Koontz 2013-10-23 22:08:13 UTC
Verified by Intel:
Reproduced error on kernel-2.6.32-358.18.1.el6.x86_64

Verified fixed in kernel-2.6.32-421.el6.x86_64

Comment 10 errata-xmlrpc 2013-11-21 22:26:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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