From: Davide Libenzi <davidel@xmailserver.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
mtk.manpages@gmail.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 15/18] flag parameters: NONBLOCK in timerfd_create
Date: Tue, 6 May 2008 15:45:21 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0805061542250.25162@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <200805062118.m46LI72i004086@devserv.devel.redhat.com>
On Tue, 6 May 2008, Ulrich Drepper wrote:
> diff --git a/fs/timerfd.c b/fs/timerfd.c
> index c6ef5e3..75d44ef 100644
> --- a/fs/timerfd.c
> +++ b/fs/timerfd.c
> @@ -184,7 +184,7 @@ asmlinkage long sys_timerfd_create(int clockid, int flags)
> int ufd;
> struct timerfd_ctx *ctx;
>
> - if (flags & ~TFD_CLOEXEC)
> + if (flags & ~(TFD_CLOEXEC | TFD_NONBLOCK))
> return -EINVAL;
> if (clockid != CLOCK_MONOTONIC &&
> clockid != CLOCK_REALTIME)
> @@ -199,7 +199,7 @@ asmlinkage long sys_timerfd_create(int clockid, int flags)
> hrtimer_init(&ctx->tmr, clockid, HRTIMER_MODE_ABS);
>
> ufd = anon_inode_getfd("[timerfd]", &timerfd_fops, ctx,
> - flags & O_CLOEXEC);
> + flags & (O_CLOEXEC | O_NONBLOCK));
> if (ufd < 0)
> kfree(ctx);
This is perfectly fine for me. Since the flags space for these new
syscalls is almost empty, it makes perfect sense to just map them to the
original O_* flags.
Acked-by: Davide Libenzi <davidel@xmailserver.org>
(for the whole serie)
- Davide
prev parent reply other threads:[~2008-05-06 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:18 Ulrich Drepper
2008-05-06 22:45 ` Davide Libenzi [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=Pine.LNX.4.64.0805061542250.25162@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--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 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®