From: Greg KH <gregkh@linuxfoundation.org>
To: "Karan Tilak Kumar (kartilak)" <kartilak@cisco.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Arulprabhu Ponnusamy (arulponn)" <arulponn@cisco.com>,
"Sesidhar Baddela (sebaddel)" <sebaddel@cisco.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Subject: Re: Request to backport commit id: 15924b0503630016dee4dbb945a8df4df659070b to 6.5/scsi-fixes
Date: Sat, 16 Sep 2023 13:37:04 +0200 [thread overview]
Message-ID: <2023091622-cryptic-pointless-b2ce@gregkh> (raw)
In-Reply-To: <SJ0PR11MB58965FCA74A2B0DD13E965A8C3F7A@SJ0PR11MB5896.namprd11.prod.outlook.com>
On Thu, Sep 14, 2023 at 04:20:24AM +0000, Karan Tilak Kumar (kartilak) wrote:
> (Re-sending email since the previous email was undeliverable due to HTML content)
>
> Hi Team,
>
> This is a request to backport the following fix to 6.5/scsi-fixes. This was merged into Linus' tree.
What is "6.5/scsi-fixes"?
> This fix fixes a crash due to a null pointer exception when a lun reset is issued from sgreset for a lun.
> With this fix, there is no longer a crash.
>
> I have another fix, which I have tested, dependent on this fix. It is currently in the pipeline.
> I'll send out a patch for that fix when the internal review is complete.
>
> Please let me know if you need any more information to backport this fix.
It doesn't apply as-is so how did you test this on the 6.5 tree? Please
provide a working, and tested, backport and we will be glad to queue it
up for the stable trees.
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-16 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 4:20 Request to backport commit id: 15924b0503630016dee4dbb945a8df4df659070b to 6.5/scsi-fixes Karan Tilak Kumar (kartilak)
2023-09-16 11:37 ` Greg KH [this message]
2023-09-19 18:35 ` Karan Tilak Kumar (kartilak)
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=2023091622-cryptic-pointless-b2ce@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arulponn@cisco.com \
--cc=kartilak@cisco.com \
--cc=martin.petersen@oracle.com \
--cc=sebaddel@cisco.com \
--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.