Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b8d897ab authored by Christoph Hellwig's avatar Christoph Hellwig Committed by Martin K. Petersen
Browse files

scsi: bfa: don't reset max_segments for every bsg request 



We already support 256 or more segments as long as the architecture
supports SG chaining (all the ones that matter do), so removed the weird
playing with limits from the job handler.

Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
Reviewed-by: default avatarHannes Reinecke <hare@suse.com>
Reviewed-by: default avatarJohannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
parent 8712f467

drivers/scsi/bfa/bfad_bsg.c

+0 −7
Original line number Diff line number Diff line
@@ -3137,16 +3137,9 @@ bfad_im_bsg_vendor_request(struct bsg_job *job) 
	uint32_t vendor_cmd = bsg_request->rqst_data.h_vendor.vendor_cmd[0];

	struct bfad_im_port_s *im_port = shost_priv(fc_bsg_to_shost(job));

	struct bfad_s *bfad = im_port->bfad;

	struct request_queue *request_q = job->req->q;

	void *payload_kbuf;

	int rc = -EINVAL;



	/*

	 * Set the BSG device request_queue size to 256 to support

	 * payloads larger than 512*1024K bytes.

	 */

	blk_queue_max_segments(request_q, 256);



	/* Allocate a temp buffer to hold the passed in user space command */

	payload_kbuf = kzalloc(job->request_payload.payload_len, GFP_KERNEL);

	if (!payload_kbuf) {