All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: patch series moving compat syscalls from fs/compat.c
Date: Mon, 24 Apr 2017 01:55:30 +0100	[thread overview]
Message-ID: <20170424005530.GU29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20170424103134.48baba07@canb.auug.org.au>

On Mon, Apr 24, 2017 at 10:31:34AM +1000, Stephen Rothwell wrote:
> Hi Al,
> 
> I couldn't easily find this patch series posted anywhere (I didn't try
> too hard) so I sill just comment here.  I first noticed them in the vfs
> tree in linux-next today.
> 
> Overall, I like what they day, but when I first created kernel/compat.c
> (in 2002), Linus did not want the compat code sprinkled all over the
> other files (due to the uglifiying effect of #ifdefs in the C code, and
> because the compat layer was only secondary).  He may have changed his
> mind since then, but it is worth asking.  The cleanups (including more
> static functions) make it worth while for me, at least.
> 
> It also might have been worth asking the original (and subsequent)
> authors of the code for review and/or comments.

	FWIW, the same kind of stuff had been done before (e.g. compat
variants of readv/writev moved to fs/read_write.c, compat aio syscalls
to fs/aio.c, etc.) with no objections from anybody.

The situation with kernel/compat.c is slightly different, but fs/compat.c
contains very little shared infrastructure - almost all of it is straight
"here's compat variant of this syscall, making use of the guts of the
native one".

  reply	other threads:[~2017-04-24  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  0:31 patch series moving compat syscalls from fs/compat.c Stephen Rothwell
2017-04-24  0:55 ` Al Viro [this message]
2017-04-24  2:57   ` Stephen Rothwell

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=20170424005530.GU29622@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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.