From: Dingisoul <dingiso.kernel@gmail.com>
To: dave.hansen@intel.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com,
dingiso.kernel@gmail.com, hpa@zytor.com, jarkko@kernel.org,
linux-sgx@vger.kernel.org, mingo@redhat.com,
shuangpeng.kernel@gmail.com, tglx@kernel.org, x86@kernel.org
Subject: Re: Re: [BUG] x86/sgx: missing kref_put() in sgx_encl_mm_add() error path
Date: Mon, 30 Mar 2026 17:25:55 -0400 [thread overview]
Message-ID: <20260330212555.880843-1-dingiso.kernel@gmail.com> (raw)
In-Reply-To: <6d6fad13-762d-488e-a0b2-86704af64f33@intel.com>
Hi Dave,
Thanks for the confirmation and the suggestion.
Moving the kref_get() after the successful mmu_notifier
registration looks great and keeps the error path clean.
Should we send a formal patch?
next prev parent reply other threads:[~2026-03-30 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 21:09 [BUG] x86/sgx: missing kref_put() in sgx_encl_mm_add() error path Dingisoul
2026-03-30 21:15 ` Dave Hansen
2026-03-30 21:25 ` Dingisoul [this message]
2026-04-08 8:58 ` Jarkko Sakkinen
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=20260330212555.880843-1-dingiso.kernel@gmail.com \
--to=dingiso.kernel@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shuangpeng.kernel@gmail.com \
--cc=tglx@kernel.org \
--cc=x86@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 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.