From: Oded Gabbay <oded.gabbay@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [git pull v2] habanalabs fixes for 5.2-rc2/3
Date: Fri, 24 May 2019 22:49:30 +0300 [thread overview]
Message-ID: <20190524194930.GA13219@ogabbay-VM> (raw)
Hi Greg,
This is the pull request containing fixes for 5.2-rc2/3. It is now
correctly rebased on your char-misc-linux branch.
It supersedes the pull request from 12/5, so you can discard that pull
request, as I see you didn't merge it anyway.
It contains 3 fixes and 1 change to a new IOCTL that was introduced to
kernel 5.2 in the previous pull requests.
See the tag comment for more details.
Thanks,
Oded
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-fixes-2019-05-24
for you to fetch changes up to 8d45f1de3994c566cb5ce9b3cb07ff1518e68ddb:
habanalabs: Avoid using a non-initialized MMU cache mutex (2019-05-24 22:46:15 +0300)
----------------------------------------------------------------
This tag contains the following fixes:
- Halt debug engines when user process closes the FD. We can't allow the
device to issue transactions for a user which doesn't exists anymore.
- Fix various security holes in debugfs API.
- Add a new opcode to the DEBUG IOCTL API. The opcode is designed
for setting the device into and out of debug mode. Although not a fix
per-se, because this is a new IOCTL which is upstreamed in kernel 5.2, I
think this is justified at this point because we won't be able to change
the API later.
- Fix a bug where the code used an uninitialized mutex
----------------------------------------------------------------
Jann Horn (1):
habanalabs: fix debugfs code
Oded Gabbay (1):
uapi/habanalabs: add opcode for enable/disable device debug mode
Omer Shpigelman (1):
habanalabs: halt debug engines on user process close
Tomer Tayar (1):
habanalabs: Avoid using a non-initialized MMU cache mutex
drivers/misc/habanalabs/context.c | 6 +++
drivers/misc/habanalabs/debugfs.c | 60 ++++++++-------------------
drivers/misc/habanalabs/device.c | 2 +
drivers/misc/habanalabs/goya/goya.c | 3 +-
drivers/misc/habanalabs/goya/goyaP.h | 1 +
drivers/misc/habanalabs/goya/goya_coresight.c | 17 ++++++++
drivers/misc/habanalabs/habanalabs.h | 2 +
drivers/misc/habanalabs/mmu.c | 8 +---
include/uapi/misc/habanalabs.h | 22 +++++++++-
9 files changed, 69 insertions(+), 52 deletions(-)
next reply other threads:[~2019-05-24 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 19:49 Oded Gabbay [this message]
2019-05-31 16:08 ` [git pull v2] habanalabs fixes for 5.2-rc2/3 Oded Gabbay
2019-05-31 16:20 ` Greg Kroah-Hartman
2019-05-31 16:21 ` Greg KH
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=20190524194930.GA13219@ogabbay-VM \
--to=oded.gabbay@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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