From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: ashutosh.dixit@intel.com, linux-kernel@vger.kernel.org
Subject: Re: scif_insert_vma()
Date: Wed, 20 Mar 2019 12:26:07 +0200 [thread overview]
Message-ID: <20190320102607.GA9457@linux.intel.com> (raw)
In-Reply-To: <1552888060.22480.197.camel@intel.com>
On Sun, Mar 17, 2019 at 10:47:40PM -0700, Sudeep Dutt wrote:
> On Mon, 2019-03-11 at 08:45 +0200, Jarkko Sakkinen wrote:
> > Hi
> >
> > Just wondering what will happen if kzalloc() fails in scif_mmap.c. How
> > it is recovered? I don't see anything in the VMA callbacks taking care
> > of this.
>
> Hi Jarkko,
>
> scif_insert_vma(..) is called from scif_mmap(..) and scif_vma_open(..).
> scif_mmap(..) checks for allocation failures but scif_vma_open(..) does
> not on purpose.
>
> The vm_operations_struct open(..)/close(..) callbacks do not allow
> returning errors. The driver will take a reference to the VMA private
> data structure irrespective of whether the allocation during the
> open(..) callback succeeds or fails. The close(..) callback cleans up
> the data structures from the mmap(..) or open(..) callbacks if any.
I'm doing allocations also in SGX vma_open callback and was grepping
through kernel tree for how allocations were handled. Thanks for
clarifying this. In SGX's case I ended up with allowing to fail in
vma open and doing SIGBUS in the #PF handler if so...
/Jarkko
prev parent reply other threads:[~2019-03-20 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 6:45 scif_insert_vma() Jarkko Sakkinen
2019-03-18 5:47 ` scif_insert_vma() Sudeep Dutt
2019-03-20 10:26 ` Jarkko Sakkinen [this message]
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=20190320102607.GA9457@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.dutt@intel.com \
/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
Powered by JetHome