From: Greg KH <gregkh@linuxfoundation.org>
To: "Jan Höppner" <hoeppner@linux.ibm.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.4.y] s390/dasd: add missing discipline function
Date: Wed, 15 Mar 2023 12:42:41 +0100 [thread overview]
Message-ID: <ZBGvMSCI8psvK0wo@kroah.com> (raw)
In-Reply-To: <ZBGuD7WnuM1hTich@kroah.com>
On Wed, Mar 15, 2023 at 12:37:51PM +0100, Greg KH wrote:
> On Wed, Mar 15, 2023 at 10:45:32AM +0100, Jan Höppner wrote:
> > From: Stefan Haberland <sth@linux.ibm.com>
> >
> > Fix crash with illegal operation exception in dasd_device_tasklet.
> > Commit b72949328869 ("s390/dasd: Prepare for additional path event handling")
> > renamed the verify_path function for ECKD but not for FBA and DIAG.
> > This leads to a panic when the path verification function is called for a
> > FBA or DIAG device.
> >
> > Fix by defining a wrapper function for dasd_generic_verify_path().
> >
> > Fixes: b72949328869 ("s390/dasd: Prepare for additional path event handling")
> > Cc: <stable@vger.kernel.org> #5.11
> > Reviewed-by: Jan Hoeppner <hoeppner@linux.ibm.com>
> > Signed-off-by: Stefan Haberland <sth@linux.ibm.com>
> > Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> > Link: https://lore.kernel.org/r/20210525125006.157531-2-sth@linux.ibm.com
> > Signed-off-by: Jens Axboe <axboe@kernel.dk>
> > ---
> > drivers/s390/block/dasd_diag.c | 7 ++++++-
> > drivers/s390/block/dasd_fba.c | 7 ++++++-
> > drivers/s390/block/dasd_int.h | 1 -
> > 3 files changed, 12 insertions(+), 3 deletions(-)
>
> What is the git commit id of this change in Linus's tree?
Nevermind, I dug in the tree and found it...
prev parent reply other threads:[~2023-03-15 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 9:31 FAILED: patch "[PATCH] s390/dasd: add missing discipline function" failed to apply to 5.4-stable tree gregkh
2023-03-15 9:45 ` [PATCH 5.4.y] s390/dasd: add missing discipline function Jan Höppner
2023-03-15 11:37 ` Greg KH
2023-03-15 11:42 ` 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=ZBGvMSCI8psvK0wo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hoeppner@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).