From: Greg KH <greg@kroah.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sasha Levin <sashal@kernel.org>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: need to back port ("scsi: ufs: Unlock on a couple error paths")
Date: Wed, 5 May 2021 09:55:12 +0200 [thread overview]
Message-ID: <YJJPYNE1azQ49ocv@kroah.com> (raw)
In-Reply-To: <20210504184635.GT21598@kadam>
On Tue, May 04, 2021 at 09:46:35PM +0300, Dan Carpenter wrote:
> Hi,
>
> I ran Smatch on 5.4.116 and I found that we were missing commit
> bb14dd1564c9 ("scsi: ufs: Unlock on a couple error paths").
>
> The problem was caused because somehow my Fixes tag did not match the
> upstream commit that stable used. I have both hashes in my git tree and
> the patches are identical except for the hash. I don't know git well
> enough to say what went wrong. I don't think the SCSI tree rebases?
>
> My fixes tag:
> Fixes: a276c19e3e98 ("scsi: ufs: Avoid busy-waiting by eliminating tag conflicts")
> ^^^^^^^^^^^^
>
> Stable hash:
> commit a8d2d45c70c7391386baf7863674f156da56a3d5
> Author: Bart Van Assche <bvanassche@acm.org>
> Date: Mon Dec 9 10:13:08 2019 -0800
>
> scsi: ufs: Avoid busy-waiting by eliminating tag conflicts
>
> [ Upstream commit 7252a3603015f1fd04363956f4b72a537c9f9c42 ]
> ^^^^^^^^^^^^
> regards,
> dan carpenter
Thanks for catching this, now queued up.
greg k-h
prev parent reply other threads:[~2021-05-05 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 18:46 need to back port ("scsi: ufs: Unlock on a couple error paths") Dan Carpenter
2021-05-04 20:07 ` Martin K. Petersen
2021-05-06 9:39 ` handling Fixes tags on rebased trees Dan Carpenter
2021-05-06 9:49 ` Greg KH
2021-05-05 7:55 ` Greg KH [this message]
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=YJJPYNE1azQ49ocv@kroah.com \
--to=greg@kroah.com \
--cc=bvanassche@acm.org \
--cc=dan.carpenter@oracle.com \
--cc=martin.petersen@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@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.