From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Maor Gottlieb <maorg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-rc] IB/uverbs: Fix NULL pointer dereference during device removal
Date: Wed, 16 Aug 2017 12:54:47 -0400 [thread overview]
Message-ID: <1502902487.33760.18.camel@redhat.com> (raw)
In-Reply-To: <20170816155704.23997-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Wed, 2017-08-16 at 18:57 +0300, Leon Romanovsky wrote:
> From: Maor Gottlieb <maorg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>
> As part of ib_uverbs_remove_one which might be triggered upon
> reset flow, we trigger IB_EVENT_DEVICE_FATAL event to userspace
> application.
> If device was removed after uverbs fd was opened but before
> ib_uverbs_get_context was called, the event file will be accessed
> before it was allocated, result in NULL pointer dereference:
Thanks, applied to -rc.
Are there any more -rc patches waiting in the works over there? As per
my other email, I'm trying to process the -rc today...
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-16 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 15:57 [PATCH rdma-rc] IB/uverbs: Fix NULL pointer dereference during device removal Leon Romanovsky
[not found] ` <20170816155704.23997-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-08-16 16:54 ` Doug Ledford [this message]
[not found] ` <1502902487.33760.18.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-16 17:46 ` Leon Romanovsky
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=1502902487.33760.18.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maorg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.