From: Byron Stanoszek <bstanoszek@comtime.com>
To: Kyle McMartin <kyle@parisc-linux.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ulrich Drepper <drepper@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
torvalds@linux-foundation.org, Chris Zankel <chris@zankel.net>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Date: Fri, 1 Jun 2007 15:17:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706011510220.26938@winds.org> (raw)
In-Reply-To: <20070601030754.GB14217@fattire.cabal.ca>
On Thu, 31 May 2007, Kyle McMartin wrote:
> On Fri, Jun 01, 2007 at 11:38:40AM +1000, Stephen Rothwell wrote:
>> This also breaks Alpha (which uses 02000000 for O_DIRECT) and parisc
>> (which uses 02000000 for O_RSYNC). So you ether need to choose a
>> different value or define O_CLOEXEC for those two architectures.
>>
>
> That's easy enough to fix...
>
> Signed-off-by: Kyle McMartin <kyle@parisc-linux.org>
>
> diff --git a/include/asm-parisc/fcntl.h b/include/asm-parisc/fcntl.h
> index 317851f..4ca0fb0 100644
> --- a/include/asm-parisc/fcntl.h
> +++ b/include/asm-parisc/fcntl.h
> @@ -14,6 +14,7 @@
> #define O_DSYNC 01000000 /* HPUX only */
> #define O_RSYNC 02000000 /* HPUX only */
> #define O_NOATIME 04000000
> +#define O_CLOEXEC 08000000 /* set close_on_exec */
>
> #define O_DIRECTORY 00010000 /* must be a directory */
> #define O_NOFOLLOW 00000200 /* don't follow links */
These are octal values, so you really want to use 010000000 instead of
08000000. :-)
While looking at that file further, I noticed these two flags share the same
value. I don't know DMAPI/XDSM, but could they potentially conflict?
#define O_NOATIME 04000000
#define O_INVISIBLE 04000000 /* invisible I/O, for DMAPI/XDSM */
Regards,
-Byron
--
Byron Stanoszek Ph: (330) 644-3059
Systems Programmer Fax: (330) 644-8110
Commercial Timesharing Inc. Email: byron@comtime.com
next prev parent reply other threads:[~2007-06-01 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:09 Ulrich Drepper
2007-05-31 18:22 ` Nicholas Miell
2007-05-31 18:32 ` Ulrich Drepper
2007-05-31 18:35 ` Davide Libenzi
2007-05-31 18:42 ` Ulrich Drepper
2007-05-31 18:46 ` Davide Libenzi
2007-05-31 18:53 ` Ulrich Drepper
2007-05-31 19:02 ` Jakub Jelinek
2007-05-31 19:17 ` Davide Libenzi
2007-05-31 19:50 ` Ulrich Drepper
2007-05-31 20:23 ` Davide Libenzi
2007-05-31 19:59 ` Linus Torvalds
2007-05-31 23:20 ` Andrew Morton
2007-06-01 1:05 ` Stephen Rothwell
2007-06-01 1:38 ` Stephen Rothwell
2007-06-01 3:07 ` Kyle McMartin
2007-06-01 19:17 ` Byron Stanoszek [this message]
2007-06-01 22:55 ` Kyle McMartin
2007-06-10 2:29 ` dean gaudet
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.0706011510220.26938@winds.org \
--to=bstanoszek@comtime.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=drepper@redhat.com \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parisc-linux@lists.parisc-linux.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 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®