aboutsummaryrefslogtreecommitdiffstats
path: root/security/keys/proc.c
diff options
context:
space:
mode:
authorTejun Heo <htejun@gmail.com>2007-01-16 21:34:02 -0500
committerJeff Garzik <jeff@garzik.org>2007-01-19 19:18:49 -0500
commit501e0c500217e38276d61445ee0839b3f2c66d05 (patch)
treeb84db101bc9c68dd37aae7eba062abde5001ad80 /security/keys/proc.c
parent96bc103f4c4e470d82ba5e372191d02ad715da45 (diff)
libata: initialize qc->dma_dir to DMA_NONE
libata didn't used to init qc->dma_dir to any specific value on qc initialization and command translation path didn't set qc->dma_dir if the command doesn't need data transfer. This made non-data commands to have random qc->dma_dir. This usually doesn't cause problem because LLDs usually check qc->protocol first and look at qc->dma_dir iff the command needs data transfer but this doesn't hold for all LLDs. It might be worthwhile to rename qc->dma_dir to qc->data_dir as we use the field to tag data direction for both PIO and DMA protocols. This problem has been spotted by James Bottomley. Signed-off-by: Tejun Heo <htejun@gmail.com> Cc: James Bottomley <James.Bottomley@SteelEye.com> Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'security/keys/proc.c')
0 files changed, 0 insertions, 0 deletions