From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: "Ismail, Mustafa" <mustafa.ismail@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Yevgeny Kliteynik <kliteyn@mellanox.com>,
Tziporet Koren <tziporet@mellanox.com>,
Alex Polak <alexpo@mellanox.com>,
Boris Pismenny <borisp@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>
Subject: Re: [PATCH 4.4 29/57] RDMA/uverbs: Check port number supplied by user verbs cmds
Date: Mon, 17 Jul 2017 21:22:15 +0200 [thread overview]
Message-ID: <20170717192215.GA2535@kroah.com> (raw)
In-Reply-To: <32E1700B9017364D9B60AED9960492BC34341BF7@fmsmsx120.amr.corp.intel.com>
On Mon, Jul 17, 2017 at 05:30:45PM +0000, Marciniszyn, Mike wrote:
> > Subject: Re: [PATCH 4.4 29/57] RDMA/uverbs: Check port number supplied
> > by user verbs cmds
> >
> > On Thu, Jul 13, 2017 at 03:54:28PM +0000, Ismail, Mustafa wrote:
> > > > Subject: [PATCH 4.4 29/57] RDMA/uverbs: Check port number supplied
> > by
> > > > user verbs cmds
> > > >
> > > > 4.4-stable review patch. If anyone has any objections, please let me
> > know.
> > >
> > > Yes, this breaks modify qp.
> > > See https://patchwork.kernel.org/patch/9830663/
> >
> > I don't understand this response at all, sorry.
> >
> > What should I do about this? Is this patch alone a problem? Is there
> > some other patch I should apply that is in Linus's tree? Where is the
> > problem, only in this old release?
> >
> > totally confused,
> >
>
> This patch utterly breaks qib and hfi1 on at least 4.10.11 stable kernel.
>
> I suspect and will soon verify that v4.13-rc1 is broke as well.
it should be broken, see the patches submitted already to fix it :)
next prev parent reply other threads:[~2017-07-17 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170713153957.515045341@linuxfoundation.org>
[not found] ` <20170713153959.566717957@linuxfoundation.org>
2017-07-13 15:54 ` [PATCH 4.4 29/57] RDMA/uverbs: Check port number supplied by user verbs cmds Ismail, Mustafa
[not found] ` <5C5647B5F4794941BAAC07CF28785CBC33E4E81F-96pTJSsuoYSkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-07-13 16:25 ` Greg Kroah-Hartman
[not found] ` <20170713162540.GB22870-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-07-13 18:44 ` Ismail, Mustafa
[not found] ` <5C5647B5F4794941BAAC07CF28785CBC33E4EC25-96pTJSsuoYSkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-07-14 6:49 ` Greg Kroah-Hartman
[not found] ` <20170714064908.GC16816-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-07-14 14:54 ` Ismail, Mustafa
2017-07-17 17:30 ` Marciniszyn, Mike
2017-07-17 19:22 ` Greg Kroah-Hartman [this message]
2017-07-17 19:24 ` Marciniszyn, Mike
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=20170717192215.GA2535@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexpo@mellanox.com \
--cc=borisp@mellanox.com \
--cc=dledford@redhat.com \
--cc=kliteyn@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=mustafa.ismail@intel.com \
--cc=stable@vger.kernel.org \
--cc=tziporet@mellanox.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