Am Dienstag, den 21.02.2006, 11:36 +0100 schrieb Joerg Schilling: > I did write some time ago that the most probable cause for the Linux > bug is that > Linux is sending uninitialized data for the amount of bytes that pad > to 12 byte. How are they supposed to be filled? I don't have a clue on the low-level stuff involved, but isn't this as simple as initializing the rest of the c array in idescsi_pc_t to 0? -- Christian Neumair <[email protected]>
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Albert Cahalan <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "D. Hazelton" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "D. Hazelton" <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- Prev by Date: Re: [PATCH] x86_64 stack trace cleanup
- Next by Date: Re: ~5x greater CPU load for a networked application when using 2.6.15-rt15-smp vs. 2.6.12-1.1390_FC4
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):
 |