linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: intel-sgx-kernel-dev@ml01.01.org
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	linux-kernel@vger.kernel.org (open list),
	platform-driver-x86@vger.kernel.org (open list:X86 PLATFORM
	DRIVERS)
Subject: [PATCH 0/3] Get rid of BUG()
Date: Thu, 26 Jan 2017 23:20:35 +0200	[thread overview]
Message-ID: <20170126212038.12809-1-jarkko.sakkinen@linux.intel.com> (raw)

The use of BUG() is not favored for any new kernel code. This patch set
implements more reasonable error recovery. In all cases the recovery is not
ideal but it is an improvement to the current situation.

In addition, sgx_free_page() has been simplified by removing the parameter for
skipping EREMOVE. EREMOVE can be successfully executed for an unused EPC page.

Jarkko Sakkinen (3):
  intel_sgx: do not use BUG() in sgx_free_page()
  intel_sgx: remove flags parameter from sgx_free_page()
  intel_sgx: fix error paths for EBLOCK and ETRACK

 drivers/platform/x86/intel_sgx.h            |  4 +-
 drivers/platform/x86/intel_sgx_ioctl.c      | 12 ++--
 drivers/platform/x86/intel_sgx_page_cache.c | 89 +++++++++++++++--------------
 drivers/platform/x86/intel_sgx_util.c       |  6 +-
 drivers/platform/x86/intel_sgx_vma.c        |  6 +-
 5 files changed, 55 insertions(+), 62 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-01-26 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 21:20 Jarkko Sakkinen [this message]
2017-01-26 21:20 ` [PATCH 1/3] intel_sgx: do not use BUG() in sgx_free_page() Jarkko Sakkinen
2017-01-27 15:45   ` Andy Shevchenko
2017-01-29 15:11     ` Jarkko Sakkinen
2017-01-28 13:32 ` [PATCH 0/3] Get rid of BUG() Andy Shevchenko

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=20170126212038.12809-1-jarkko.sakkinen@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=intel-sgx-kernel-dev@ml01.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).