From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Marciniszyn <mike.marciniszyn@intel.com>
Cc: stable@vger.kernel.org, linux-rdma@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: [PATCH] IB/hfi1: Incorrect sizing of sge for PIO will OOPs
Date: Sat, 5 Jan 2019 09:22:58 +0100 [thread overview]
Message-ID: <20190105082258.GA31491@kroah.com> (raw)
In-Reply-To: <20190102175907.18332.56448.stgit@scvm10.sc.intel.com>
On Wed, Jan 02, 2019 at 09:59:10AM -0800, Mike Marciniszyn wrote:
> From: Michael J. Ruhl <michael.j.ruhl@intel.com>
>
> Upstream commit dbc2970caef74e8ff41923d302aa6fb5a4812d0e.
>
> An incorrect sge sizing in the HFI PIO path will cause an OOPs similar to
> this:
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [] hfi1_verbs_send_pio+0x3d8/0x530 [hfi1]
> PGD 0
> Oops: 0000 1 SMP
> Call Trace:
> ? hfi1_verbs_send_dma+0xad0/0xad0 [hfi1]
> hfi1_verbs_send+0xdf/0x250 [hfi1]
> ? make_rc_ack+0xa80/0xa80 [hfi1]
> hfi1_do_send+0x192/0x430 [hfi1]
> hfi1_do_send_from_rvt+0x10/0x20 [hfi1]
> rvt_post_send+0x369/0x820 [rdmavt]
> ib_uverbs_post_send+0x317/0x570 [ib_uverbs]
> ib_uverbs_write+0x26f/0x420 [ib_uverbs]
> ? security_file_permission+0x21/0xa0
> vfs_write+0xbd/0x1e0
> ? mntput+0x24/0x40
> SyS_write+0x7f/0xe0
> system_call_fastpath+0x16/0x1b
>
> Fix by adding the missing sizing check to correctly determine the sge
> length.
>
> Fixes: 7724105686e7 ("IB/hfi1: add driver files")
> Cc: <stable@vger.kernel.org> # 4.9.x+
This fails to apply to 4.9.y :(
next prev parent reply other threads:[~2019-01-05 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 17:59 [PATCH] IB/hfi1: Incorrect sizing of sge for PIO will OOPs Mike Marciniszyn
2019-01-05 8:22 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-07 14:43 Mike Marciniszyn
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=20190105082258.GA31491@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=stable-commits@vger.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.