mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: <ira.weiny@intel.com>, <linux-api@vger.kernel.org>
Cc: <x86@kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-kselftest@vger.kernel.org>
Subject: Re: [RFC PATCH 0/6] User pkey minor bug fixes
Date: Mon, 13 Jun 2022 15:05:30 -0700	[thread overview]
Message-ID: <948bc7f4-f1c0-9b79-0eac-df8659b22753@intel.com> (raw)
In-Reply-To: <20220610233533.3649584-1-ira.weiny@intel.com>

On 6/10/2022 4:35 PM, ira.weiny@intel.com wrote:

> 
> glibc says it returns ENOSYS if the system does not support pkeys but I don't
> see where ENOSYS is returned?  AFAICS it just returns what the kernel returns.
> So it is probably up to user of glibc.
> 

Implementation of the pkeys system calls is arch specific and 
conditional. See kernel/sys_ni.c

glibc is probably talking about ENOSYS being returned when the 
architecture doesn't have support or the CONFIG option is disabled on 
supported architectures.

Thanks,
Sohil

      parent reply	other threads:[~2022-06-13 22:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 23:35 ira.weiny
2022-06-10 23:35 ` [RFC PATCH 1/6] testing/pkeys: Add command line options ira.weiny
2022-06-13 22:31   ` Sohil Mehta
2022-06-13 23:41     ` Ira Weiny
2022-06-10 23:35 ` [RFC PATCH 2/6] testing/pkeys: Don't use uninitialized variable ira.weiny
2022-06-13 22:48   ` Sohil Mehta
2022-06-13 23:59     ` Ira Weiny
2022-06-10 23:35 ` [RFC PATCH 3/6] testing/pkeys: Add additional test for pkey_alloc() ira.weiny
2022-06-16 19:25   ` Sohil Mehta
2022-06-16 20:24     ` Dave Hansen
2022-06-10 23:35 ` [RFC PATCH 4/6] pkeys: Lift pkey hardware check " ira.weiny
2022-06-16 19:31   ` Sohil Mehta
2022-06-10 23:35 ` [RFC PATCH 5/6] pkeys: Up level pkey_free() checks ira.weiny
2022-06-13  9:14   ` Christophe Leroy
2022-06-10 23:35 ` [RFC PATCH 6/6] pkeys: Change mm_pkey_free() to void ira.weiny
2022-06-13  9:17   ` Christophe Leroy
2022-06-13 16:16     ` Ira Weiny
2022-06-13 22:05 ` Sohil Mehta [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=948bc7f4-f1c0-9b79-0eac-df8659b22753@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®