From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 188961] New: Function mvs_task_prep() returns improper values on failures
Date: Fri, 25 Nov 2016 11:12:35 +0000 [thread overview]
Message-ID: <bug-188961-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=188961
Bug ID: 188961
Summary: Function mvs_task_prep() returns improper values on
failures
Product: SCSI Drivers
Version: 2.5
Kernel Version: linux-4.9-rc6
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: bianpan2010@ruc.edu.cn
Regression: No
The function mvs_task_prep() defined in file drivers/scsi/mvsas/mv_sas.c
returns 0 on success, or non-zero values on failures. It calls function
pci_pool_alloc() and checks its return value against NULL (at line 794), and if
the return value is NULL, the control flow jumps to label "err_out_tag", cleans
allocated memory and returns variable rc. Function pci_pool_alloc() is called
after the check of variable rc, so the value of rc must be 0. As a result,
mvs_task_prep() will return 0 (indicates success) even the call to
pci_pool_alloc() fails. I think it is better to assign "-ENOMEM" to rc when
pci_pool_alloc() fails. Codes and comments related to this bug are summarised
as follows.
mvs_task_prep @@ drivers/scsi/mvsas/mv_sas.c
711 static int mvs_task_prep(struct sas_task *task, struct mvs_info *mvi, int
is_tmf,
712 struct mvs_tmf_task *tmf, int *pass)
713 {
...
719 int rc = 0;
...
783 rc = mvs_tag_alloc(mvi, &tag);
784 if (rc)
785 goto err_out;
786
787 slot = &mvi->slot_info[tag];
788
789 task->lldd_task = NULL;
790 slot->n_elem = n_elem;
791 slot->slot_tag = tag;
792
793 slot->buf = pci_pool_alloc(mvi->dma_pool, GFP_ATOMIC, &slot->buf_dma);
794 if (!slot->buf)
// insert "rc = -ENOMEM" here?
795 goto err_out_tag;
...
838 return rc;
839
840 err_out_slot_buf:
841 pci_pool_free(mvi->dma_pool, slot->buf, slot->buf_dma);
842 err_out_tag:
843 mvs_tag_free(mvi, tag);
844 err_out:
845
846 dev_printk(KERN_ERR, mvi->dev, "mvsas prep failed[%d]!\n", rc);
847 if (!sas_protocol_ata(task->task_proto))
848 if (n_elem)
849 dma_unmap_sg(mvi->dev, task->scatter, n_elem,
850 task->data_dir);
851 prep_out:
852 return rc;
853 }
Thanks very much!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-11-25 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 11:12 bugzilla-daemon [this message]
2017-05-12 0:20 ` [Bug 188961] Function mvs_task_prep() returns improper values on failures bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-188961-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.