mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Jones <davej@redhat.com>, Fabian Frederick <fabf@skynet.be>,
	linux-kernel@vger.kernel.org, akpm <akpm@linux-foundation.org>,
	rdunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 1/1] sys_sysfs: Add CONFIG_SYSFS_SYSCALL
Date: Thu, 13 Feb 2014 14:38:32 -0800	[thread overview]
Message-ID: <20140213223832.GA14535@kroah.com> (raw)
In-Reply-To: <20140213223141.GA1232@redhat.com>

On Thu, Feb 13, 2014 at 05:31:41PM -0500, Dave Jones wrote:
> On Thu, Feb 13, 2014 at 10:09:42PM +0800, Fabian Frederick wrote:
>  > sys_sysfs is an obsolete system call no longer supported by libc ...
>  > -This patch adds a default CONFIG_SYSFS_SYSCALL=y
>  > -Option can be turned off in expert mode.
>  > -cond_syscall added to kernel/sys_ni.c
>  > 
>  > Signed-off-by: Fabian Frederick <fabf@skynet.be>
>  > ---
>  >  fs/filesystems.c |  2 ++
>  >  init/Kconfig     | 10 ++++++++++
>  >  kernel/sys_ni.c  |  1 +
>  >  3 files changed, 13 insertions(+)
> 
> did anyone ever ship userspace that actually used that syscall ?
> Some ancient version of udev that probably doesn't work on a modern kernel anyway maybe ?

sys_sysfs doesn't have anything to do with /sys/ and udev in any way
that I know of, it's a much older thing, a sysv syscall that can return
the index, name, or max index of a filesystem.

And yes, I got confused by it all the time when creating sysfs :)

thanks,

greg k-h

  reply	other threads:[~2014-02-13 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 14:09 Fabian Frederick
2014-02-13 22:31 ` Dave Jones
2014-02-13 22:38   ` Greg KH [this message]
2014-02-13 22:41     ` Dave Jones
2014-02-13 22:43   ` Andrew Morton
2014-02-19 12:49     ` Fabian Frederick

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=20140213223832.GA14535@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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®