Bug 490732

Summary: Enable CONFIG_BLK_DEV_INTEGRITY in kernel build to enable SCSI T10 DIF support
Product: Red Hat Enterprise Linux 6 Reporter: Jamie Wellnitz <jamie.wellnitz>
Component: kernelAssignee: Jeff Moyer <jmoyer>
Status: CLOSED CURRENTRELEASE QA Contact: Evan McNabb <emcnabb>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: coughlan, james.smart, jmoyer, laurie.barry, notting, rwheeler
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-11 16:12:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 534151    

Description Jamie Wellnitz 2009-03-17 18:45:42 UTC
Emulex is requesting that the RHEL 6 kernels include T10 DIF (Data Integrity Field) support by setting CONFIG_BLK_DEV_INTEGRITY=y in the kernel .config file.

Comment 1 RHEL Program Management 2009-03-17 19:13:18 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Bill Nottingham 2009-03-18 17:54:18 UTC
Marking as MODIFIED.

The feature requested has already been accepted into the upstream code base
planned for the next major release of Red Hat Enterprise Linux.

When the next milestone release of Red Hat Enterprise Linux 6 is available,
please verify that the feature requested is present and functioning as
desired.

Comment 6 releng-rhel@redhat.com 2010-11-11 16:12:27 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.