From: Meelis Roos <mroos@linux.ee>
To: "Madhani, Himanshu" <Himanshu.Madhani@cavium.com>
Cc: Dept-Eng QLA2xxx Upstream <qla2xxx-upstream@cavium.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: qla2xxx UBSAN warning in 4.14-rc1
Date: Thu, 9 Nov 2017 10:59:08 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.21.1711091058150.7113@math.ut.ee> (raw)
In-Reply-To: <79E0683A-42C7-4784-9B6A-1F7C120CA69A@cavium.com>
Hello again.
> > On Sep 18, 2017, at 3:49 AM, Meelis Roos <mroos@linux.ee> wrote:
> >
> > Hello, I decided to widen the coverage of my kernel testbed and put some
> > FC cards into servers. This one is a PCI-X QLA2340 in HP Proliant DL 380
> > G4 (first 64-bit generation of Proliants). I got a UBSAN warning from
> > qla2xxx before probing for the firmware.
> >
> > This is reproducible with or without firmware being available.
> >
> > [ 3.905570] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 10.00.00.01-k.
> > [ 3.905977] qla2xxx 0000:06:02.0: PCI IRQ 78 -> rerouted to legacy IRQ 18
> > [ 3.906172] qla2xxx [0000:06:02.0]-001d: : Found an ISP2312 irq 18 iobase 0xffffc90000139000.
> > [...]
> > [ 4.180117] ================================================================================
> > [ 4.180300] UBSAN: Undefined behaviour in drivers/scsi/qla2xxx/qla_isr.c:275:14
> > [ 4.180464] shift exponent 32 is too large for 32-bit type 'int'
> > [ 4.180576] CPU: 0 PID: 138 Comm: systemd-udevd Not tainted 4.14.0-rc1-00009-g0666f560b71b #27
> > [ 4.180741] Hardware name: HP ProLiant DL380 G4, BIOS P51 07/19/2007
> > [ 4.180849] Call Trace:
> > [ 4.180961] dump_stack+0x4e/0x6c
> > [ 4.181072] ubsan_epilogue+0xd/0x3b
> > [ 4.181179] __ubsan_handle_shift_out_of_bounds+0x112/0x14c
> > [ 4.181290] ? try_to_del_timer_sync+0x44/0x68
> > [ 4.181440] qla2x00_mbx_completion+0x1c5/0x25d [qla2xxx]
> > [ 4.182683] qla2300_intr_handler+0x1ea/0x3bb [qla2xxx]
> > [ 4.182827] qla2x00_mailbox_command+0x77b/0x139a [qla2xxx]
[...]
> we’ll take a look at this
How is it going? 4.14 is almost here but it is still unfixed?
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-11-09 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 10:49 qla2xxx UBSAN warning in 4.14-rc1 Meelis Roos
2017-09-26 21:36 ` Madhani, Himanshu
2017-11-09 8:59 ` Meelis Roos [this message]
2017-11-10 4:49 ` Himanshu Madhani
2018-01-24 20:35 ` Meelis Roos
2018-01-24 21:13 ` Bart Van Assche
2018-01-24 22:18 ` Meelis Roos
2018-01-25 7:25 ` Madhani, Himanshu
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=alpine.LRH.2.21.1711091058150.7113@math.ut.ee \
--to=mroos@linux.ee \
--cc=Himanshu.Madhani@cavium.com \
--cc=linux-scsi@vger.kernel.org \
--cc=qla2xxx-upstream@cavium.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