From: Ondrej Zary <linux@zary.sk>
To: Arun Easi <aeasi@marvell.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: NULL pointer dereference in qla24xx_abort_command
Date: Thu, 26 Mar 2020 15:36:51 +0100 [thread overview]
Message-ID: <202003261536.51981.linux@zary.sk> (raw)
In-Reply-To: <alpine.LRH.2.21.9999.2003251431090.28238@irv1user01.caveonetworks.com>
On Wednesday 25 March 2020, Arun Easi wrote:
> On Wed, 25 Mar 2020, 11:06am, Ondrej Zary wrote:
> > Hi Himanshu,
> > could you please look into this bug?
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.spinics.net_list
> >s_linux-2Dscsi_msg138637.html&d=DwICAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=XB49zT5-
> >k3oWvfMuBJCeRK5Sk6o3bkGM6ewB3QuTOME&m=ezZ2dt9wVYnM-c6jJKx9bPQ0-7vbSf5HQ0bG
> >qri_iNE&s=wriOIaA9pVuKVrGPMvcZstNdYbzcZgFVw_OKiM0idIg&e=
> >
...
>
> Ondrej,
>
> Could you pick up the latest upstream kernel and retry your test (even if
> it takes longer to reproduce)? That way we do not need to spend time on an
> issue that may have already been fixed.
The server is a backup production server so there's no room for such
experiments.
BTW. Which one is "the latest upstream kernel"? kernel.org says:
mainline: 5.6-rc7 2020-03-23
stable: 5.5.13 2020-03-25
longterm: 5.4.28 2020-03-25
longterm: 4.19.113 2020-03-25
longterm: 4.14.174 2020-03-20
longterm: 4.9.217 2020-03-20
longterm: 4.4.217 2020-03-20
longterm: 3.16.82 2020-02-11
Maybe you can point me to patches that could fix the problem?
--
Ondrej Zary
next prev parent reply other threads:[~2020-03-26 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 18:06 NULL pointer dereference in qla24xx_abort_command Ondrej Zary
2020-03-25 21:34 ` Arun Easi
2020-03-26 14:36 ` Ondrej Zary [this message]
2020-05-15 13:21 ` Ondrej Zary
2020-06-21 9:50 ` Ondrej Zary
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 18:20 Ondrej Zary
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=202003261536.51981.linux@zary.sk \
--to=linux@zary.sk \
--cc=aeasi@marvell.com \
--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.