From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Dmitry Vyukov <dvyukov@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Valdis.Kletnieks@vt.edu, sean.hefty@intel.com,
Hal Rosenstock <hal.rosenstock@gmail.com>,
linux-rdma@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] infiniband: remove WARN that is not kernel bug
Date: Wed, 14 Dec 2016 20:27:21 +0200 [thread overview]
Message-ID: <20161214182721.GA811@mtr-leonro.local> (raw)
In-Reply-To: <b5343f5e-68a8-5a01-5fa9-04e9181e4082@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Wed, Dec 14, 2016 at 01:16:45PM -0500, Doug Ledford wrote:
> On 11/21/2016 12:38 PM, Leon Romanovsky wrote:
> > On Mon, Nov 21, 2016 at 09:52:53AM -0700, Jason Gunthorpe wrote:
> >> On Mon, Nov 21, 2016 at 02:14:08PM +0200, Leon Romanovsky wrote:
> >>>>
> >>>> In ib_ucm_write function there is a wrong prefix:
> >>>>
> >>>> + pr_err_once("ucm_write: process %d (%s) tried to do something hinky\n",
> >>>
> >>> I did it intentionally to have the same errors for all flows.
> >>
> >> Lets actually use a good message too please?
> >>
> >> pr_err_once("ucm_write: process %d (%s) changed security contexts after opening FD, this is not allowed.\n",
> >>
> >> Jason
>
> I applied Leon's reworked version of this patch, thanks.
Thanks Doug,
I already forgot about it :)
>
> --
> Doug Ledford <dledford@redhat.com>
> GPG Key ID: 0E572FDD
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2016-12-14 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 10:18 [PATCH v2] infiniband: remove WARN that is not kernel bug Dmitry Vyukov
2016-11-21 10:25 ` Miroslav Benes
[not found] ` <alpine.LNX.2.00.1611211123450.22752-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2016-11-21 10:30 ` Dmitry Vyukov
2016-11-21 10:30 ` Dmitry Vyukov
[not found] ` <CACT4Y+ZO9sTbBGwNUUMkAQ5m0N-4aT0S9xypCRbBUch1pQNw9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-21 11:44 ` Leon Romanovsky
2016-11-21 11:44 ` Leon Romanovsky
2016-11-21 11:48 ` Dmitry Vyukov
[not found] ` <CACT4Y+Y1sL-8K7HhZ5M5ABVPG0kM=dKZh+6gvuNRvzXFtiA5aQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-21 12:14 ` Leon Romanovsky
2016-11-21 12:14 ` Leon Romanovsky
2016-11-21 16:52 ` Jason Gunthorpe
[not found] ` <20161121165253.GA22237-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-11-21 17:38 ` Leon Romanovsky
2016-11-21 17:38 ` Leon Romanovsky
[not found] ` <20161121173820.GC23083-2ukJVAZIZ/Y@public.gmane.org>
2016-12-14 18:16 ` Doug Ledford
2016-12-14 18:16 ` Doug Ledford
2016-12-14 18:27 ` Leon Romanovsky [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=20161214182721.GA811@mtr-leonro.local \
--to=leon@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dledford@redhat.com \
--cc=dvyukov@google.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sean.hefty@intel.com \
--cc=syzkaller@googlegroups.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 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.