From: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
To: linux-kernel@vger.kernel.org
Cc: Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 1/1] include/uapi: Define AT_FDNODIR constant as future guarantee
Date: Sat, 05 Jul 2014 19:51:19 +0000 (GMT) [thread overview]
Message-ID: <fb469d6277ef.53b85737@langara.bc.ca> (raw)
From: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca
This constant means that in the far future it might be possible to
define other AT_FD* constants.
Signed-off-by: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
---
This is my first kernel patch but this is really trivial so I hope I'm doing
this right.
diff --git a/include/uapi/linux/fcntl.h b/include/uapi/linux/fcntl.h
index 074b886..92223f0 100644
--- a/include/uapi/linux/fcntl.h
+++ b/include/uapi/linux/fcntl.h
@@ -38,9 +38,15 @@
#define DN_ATTRIB 0x00000020 /* File changed attibutes */
#define DN_MULTISHOT 0x80000000 /* Don't remove notifier */
+#define AT_FDNODDIR -1 /* Special value used to indicate
+ openat should not use any directory.
+ Currently, other values work for this
+ but in the future that might
+ change. */
#define AT_FDCWD -100 /* Special value used to indicate
- openat should use the current
- working directory. */
+ openat should use the current
+ working directory. */
+
#define AT_SYMLINK_NOFOLLOW 0x100 /* Do not follow symbolic links. */
#define AT_REMOVEDIR 0x200 /* Remove directory instead of
unlinking file. */
next reply other threads:[~2014-07-05 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 19:51 Steven Stewart-Gallus [this message]
2014-07-08 12:12 ` [PATCH 1/1] include/uapi: Define AT_FDNODIR constant as future guarantee Christoph Hellwig
2014-07-09 23:43 ` Steven Stewart-Gallus
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=fb469d6277ef.53b85737@langara.bc.ca \
--to=sstewartgallus00@mylangara.bc.ca \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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