From: Doug Ledford <dledford@redhat.com>
To: Kamal Mostafa <kamal@canonical.com>
Cc: stable@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] IB/security: restrict use of the write() interface
Date: Wed, 18 May 2016 17:40:00 -0400 [thread overview]
Message-ID: <07725b77-3275-ea07-4315-13997aeed70f@redhat.com> (raw)
In-Reply-To: <20160518204203.GB4268@whence.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On 05/18/2016 04:42 PM, Kamal Mostafa wrote:
> On Wed, May 18, 2016 at 12:41:59PM -0400, Doug Ledford wrote:
>> Upstream commit e6bd18f57aad (IB/security: Restrict use of the write()
>> interface) handled the cases for all drivers in the current upstream
>> kernel. The ipath driver had recently been deprecated and moved to
>> staging, and then removed entirely. It had the same security flaw as
>> the qib driver. Fix that up with this separate patch.
>>
>> Note: The ipath driver only supports hardware that ended production
>> over 10 years ago, so there should be none of this hardware still
>> present in the wild.
>>
>> Cc: stable@vger.kernel.org # <= 4.2.x
>> Signed-off-by: Doug Ledford <dledford@redhat.com>
>> ---
>> drivers/infiniband/hw/ipath/ipath_file_ops.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/infiniband/hw/ipath/ipath_file_ops.c b/drivers/infiniband/hw/ipath/ipath_file_ops.c
>> index 450d15965005..1f94b560d749 100644
>> --- a/drivers/infiniband/hw/ipath/ipath_file_ops.c
>> +++ b/drivers/infiniband/hw/ipath/ipath_file_ops.c
>> @@ -45,6 +45,8 @@
>> #include <linux/uio.h>
>> #include <asm/pgtable.h>
>>
>> +#include <rdma/ib.h>
>> +
>> #include "ipath_kernel.h"
>> #include "ipath_common.h"
>> #include "ipath_user_sdma.h"
>> @@ -2244,6 +2246,9 @@ static ssize_t ipath_write(struct file *fp, const char __user *data,
>> ssize_t ret = 0;
>> void *dest;
>>
>> + if (WARN_ON_ONCE(!ib_safe_file_access(fp)))
>> + return -EACCESS;
>
> (Same as for the 4.4.x patch)...
>
> This needs to be "EACCES" (one fewer 'S').
>
> Thanks, Doug. Queued up (with one fewer 'S') for 4.2 and 3.19 -stable.
Thanks for fixing it up!
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2016-05-18 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:41 [PATCH] IB/security: restrict use of the write() interface Doug Ledford
2016-05-18 20:42 ` Kamal Mostafa
2016-05-18 21:40 ` Doug Ledford [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-18 16:46 Doug Ledford
2016-05-18 20:40 ` Kamal Mostafa
2016-05-21 5:32 ` Greg KH
2016-05-18 16:58 [PATCH] IB/security: Restrict " Doug Ledford
2016-05-18 17:20 ` Greg KH
2016-05-18 17:57 ` Doug Ledford
2016-05-18 18:59 ` Or Gerlitz
2016-05-18 19:05 ` Doug Ledford
2016-05-18 19:47 ` Or Gerlitz
2016-05-18 19:59 ` Doug Ledford
2016-05-18 20:36 ` Or Gerlitz
2016-05-18 21:42 ` Doug Ledford
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=07725b77-3275-ea07-4315-13997aeed70f@redhat.com \
--to=dledford@redhat.com \
--cc=kamal@canonical.com \
--cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox