Bug 462477

Summary:	Firewire iso transmission cannot set some fields correctly
Product:	Red Hat Enterprise Linux 5	Reporter:	Jay Fenlason <fenlason>
Component:	kernel	Assignee:	Jay Fenlason <fenlason>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.3	CC:	jfeeney
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:	2013-11-04 00:27:49 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:

Description Jay Fenlason 2008-09-16 15:52:30 UTC

Description of problem:
When using the firewire stack to send iso packets, sending packets with a sy field other than 0 or 4, or a tag field other than 0 or 2 results in sending a packet with an incorrect sy or tag field.

Version-Release number of selected component (if applicable):
The 5.2 and 5.3beta kernels.

How reproducible:
Always.

Steps to Reproduce:
1.Write a program that sends iso packets with varying sy and tag values.
2.Run it and observe the output with nosy or another firewire sniffer.
3.Observe that only the 2 bit of the tag field, and the 4 bit of the sy field ever change.
  
Actual results:
Only the 2 bit of the tag field, and the 4 bit of the sy field can be set in outgoing packets.

Expected results:
Both fields should be capable of taking all legal values.

Additional info:
This bug is in two parts: one (firewire-cdev.h) will require recompiling libraries and/or applications to fix.  Since nobody has opened a bug report on this yet, it is apparent that such applications are rare.

Comment 1 John Feeney 2013-11-04 00:27:49 UTC

This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore is being closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide a sufficient business justification
in order to re-open it.