public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/clone09.c: add kernel version check
Date: Fri, 22 Sep 2017 04:57:40 -0400 (EDT)	[thread overview]
Message-ID: <986027145.19743530.1506070660802.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1505785364-22465-1-git-send-email-yangx.jy@cn.fujitsu.com>



----- Original Message -----
> 1) On all kernels which support CONFIG_NET_NS, clone(2) only could return
>    EINVAL due to disabled CONFIG_NET_NS instead of unknown flags.  Please
>    see the following kernel code in net/core/net_namespace.c:
>    --------------------------------------------------------------------
>    struct net *copy_net_ns(unsigned long flags, struct net *old_net)
>    ...
>         #ifndef CONFIG_NET_NS
>                 return ERR_PTR(-EINVAL);
>         #endif
>    --------------------------------------------------------------------
> 
>    The support is introduced in kernel:
>    '9dd776b ("[NET]: Add network namespace clone & unshare support.")'
> 
> 2) Usually, a syscall flags should always include a check of the following
>    form in its implementation:
>    ---------------------------------
>    if (flags & ~(FL_XXX | FL_YYY))
>         return -EINVAL;
>    ---------------------------------
> 
>    This check could verify unknown flags, but clone(2) does not have the
>    check and just returns 0, this issue has been around for several years,
>    and it is hardly to be fixed since doing so would break existing
>    applications.
> 
>    Please see the following URL for detailed information:
>    https://lwn.net/Articles/588444/
> 
>    It is hard to make out whether CLONE_NEWNET is supported or not by
>    returned value and errno.
> 
>    According to above reasons and clone()'s manpage, i think we should
>    add kernel version check to skip this case on an old kernel and update
>    description about EINVAL.
> 

Pushed.

Thanks,
Jan

      reply	other threads:[~2017-09-22  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  9:25 [LTP] [PATCH] syscalls/clone09.c: skip this test if net ns is not supported Xiao Yang
2017-07-20 12:17 ` Cyril Hrubis
2017-09-18 11:23   ` Xiao Yang
2017-09-19  1:42   ` [LTP] [PATCH v2] syscalls/clone09.c: add kernel version check Xiao Yang
2017-09-22  8:57     ` Jan Stancek [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=986027145.19743530.1506070660802.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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