Bug #2042

blkdev should not discard bd->d_maxxfer

Added by Alexey Zaytsev over 6 years ago. Updated almost 6 years ago.

Status:ResolvedStart date:2012-01-28
Priority:NormalDue date:
Assignee:Alexey Zaytsev% Done:


Category:driver - device drivers
Target version:-
Difficulty:Bite-size Tags:needs-triage


blkdev calculates bd->d_maxxfer parameter based on the user's dma attrs, or hard-codes it to 1M in case DMA is not used. Then it just discards the value, and uses whatever the user set in bd->d_ops.o_drive_info().

Fix: Only use the user's supplied drive.d_maxxfer as an upper bound for bd->d_maxxfer. Also, ignore it if it's zero (the user did not set it).


#1 Updated by Alexey Zaytsev about 6 years ago

  • Subject changed from blkdev should not discard bd->d_maxxfer. to blkdev should not discard bd->d_maxxfer

#2 Updated by Alexey Zaytsev almost 6 years ago

  • Status changed from New to Resolved

Also available in: Atom