[SCSI] mpt2sas: Fix for Driver oops, when loading driver with max_queue_depth command...
authorsreekanth.reddy@lsi.com <sreekanth.reddy@lsi.com>
Tue, 17 Jul 2012 10:27:05 +0000 (15:57 +0530)
committerJames Bottomley <JBottomley@Parallels.com>
Wed, 22 Aug 2012 05:38:49 +0000 (09:38 +0400)
commit338b131a3269881c7431234855c93c219b0979b6
tree741f394a7159c15ed73281ce563d5d8e3d176f9a
parent23dcfa61bac244e1200ff9ad19c6e9144dcb6bb5
[SCSI] mpt2sas: Fix for Driver oops, when loading driver with max_queue_depth command line option to a very small value

If the specified max_queue_depth setting is less than the
expected number of internal commands, then driver will calculate
the queue depth size to a negitive number. This negitive number
is actually a very large number because variable is unsigned
16bit integer. So, the driver will ask for a very large amount of
memory for message frames and resulting into oops as memory
allocation routines will not able to handle such a large request.

So, in order to limit this kind of oops, The driver need to set
the max_queue_depth to a scsi mid layer's can_queue value. Then
the overall message frames required for IO is minimum of either
(max_queue_depth plus internal commands) or the IOC global
credits.

Signed-off-by: Sreekanth Reddy <sreekanth.reddy@lsi.com>
Cc: <stable@kernel.org>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
drivers/scsi/mpt2sas/mpt2sas_base.c
This page took 0.039418 seconds and 5 git commands to generate.