mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bean Huo <beanhuo@iokpp.de>
To: Stanley Jhu <stanleyjhu@google.com>,
	"Martin K. Petersen" <mkp@kernel.org>,
	 "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
	Bart Van Assche <bvanassche@acm.org>,
	 Bean Huo <beanhuo@micron.com>,
	Peter Wang <peter.wang@mediatek.com>,
	Brian Kao <powenkao@google.com>,
	 linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 1/5] scsi: ufs: bsg: Complete the job on error
Date: Sun, 18 Oct 2026 20:21:39 +0200	[thread overview]
Message-ID: <361e83f8ae479909597238b4ddf9b3a1e40ef0c2.camel@iokpp.de> (raw)
In-Reply-To: <20261015001855.3450573-2-stanleyjhu@google.com>

On Thu, 2026-10-15 at 08:18 +0800, Stanley Jhu wrote:
> index 7a66917b3fc0..18c318d78122 100644
> --- a/drivers/ufs/core/ufs_bsg.c
> +++ b/drivers/ufs/core/ufs_bsg.c
> @@ -195,14 +195,12 @@ static int ufs_bsg_request(struct bsg_job *job)
>         ufshcd_rpm_put_sync(hba);
>         kfree(buff);
>         bsg_reply->result = ret;
> -       /* complete the job here only if no error */
> -       if (ret == 0) {
> +       if (ret == 0)
>                 job->reply_len = rpmb ? sizeof(struct ufs_rpmb_reply) :
>                                         sizeof(struct ufs_bsg_reply);
> -               bsg_job_done(job, ret, bsg_reply->reply_payload_rcv_len);
> -       }
> +       bsg_job_done(job, ret, bsg_reply->reply_payload_rcv_len);

Since the old comment is gone, it's better to add a short one before
bsg_job_done() saying we must always complete the job and return 0?

otherwise a later change could easily bring back either the leak or the double
completion that b13a3539eb2a fixed?

Reviewed-by: Bean Huo <beanhuo@micron.com>

>  
> -       return ret;
> +       return 0;
>  }


  reply	other threads:[~2026-10-18 18:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  0:18 [PATCH v2 0/5] scsi: ufs: Fix UIC result byte and BSG request handling Stanley Jhu
2026-10-15  0:18 ` [PATCH v2 1/5] scsi: ufs: bsg: Complete the job on error Stanley Jhu
2026-10-18 18:21   ` Bean Huo [this message]
2026-10-15  0:18 ` [PATCH v2 2/5] scsi: ufs: bsg: Clear the reply buffer before use Stanley Jhu
2026-10-18 18:24   ` Bean Huo
2026-10-15  0:18 ` [PATCH v2 3/5] scsi: ufs: bsg: Validate request_len before accessing request Stanley Jhu
2026-10-15  0:18 ` [PATCH v2 4/5] scsi: ufs: bsg: Reject UIC commands with a non-zero result byte Stanley Jhu
2026-10-18 18:30   ` Bean Huo
2026-10-15  0:18 ` [PATCH v2 5/5] scsi: ufs: core: Clear stale UIC result byte before peer DME retries Stanley Jhu
2026-10-18 18:35   ` Bean Huo
2026-10-15  4:39 ` [PATCH v2 0/5] scsi: ufs: Fix UIC result byte and BSG request handling Peter Wang
2026-10-15 17:53 ` Bart Van Assche
     [not found] <sashiko-outbox-172057@kernel.org>
2026-10-15  0:41 ` [PATCH v2 1/5] scsi: ufs: bsg: Complete the job on error Stanley Jhu

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=361e83f8ae479909597238b4ddf9b3a1e40ef0c2.camel@iokpp.de \
    --to=beanhuo@iokpp.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkp@kernel.org \
    --cc=peter.wang@mediatek.com \
    --cc=powenkao@google.com \
    --cc=stable@vger.kernel.org \
    --cc=stanleyjhu@google.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®