From: Bill Kendall <wkendall@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] add lpath_to_handle to libhandle
Date: Wed, 23 Dec 2009 13:21:04 -0600 [thread overview]
Message-ID: <20091223192101.GA3578@sgi.com> (raw)
In-Reply-To: <20091223131535.GA23394@infradead.org>
On Wed, Dec 23, 2009 at 08:15:35AM -0500, Christoph Hellwig wrote:
> One thing that could be changes is to also do the fspath conversion for
> block and chacater special files. While we can open those they will not
> end up in the xfs file operations and thus not provide the nessecary
> ioctl.
Parent dir is now used for all types except regular files and directories.
Special file conversions still fail, but at least it's XFS making that
decision. Also this prevents calling open on named pipes, which could
block.
> Btw, it would be nice if you could write a testcase for xfstests that
> fails with the old version on links but works with the new one.
I'll take a look at this and post a separate patch.
Signed-off-by: Bill Kendall <wkendall@sgi.com>
Index: xfsprogs-kernel.org/libhandle/handle.c
===================================================================
--- xfsprogs-kernel.org.orig/libhandle/handle.c
+++ xfsprogs-kernel.org/libhandle/handle.c
@@ -16,6 +16,7 @@
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/
+#include <libgen.h>
#include <xfs/xfs.h>
#include <xfs/handle.h>
#include <xfs/parent.h>
@@ -40,6 +41,7 @@ typedef union {
static int obj_to_handle(char *, int, unsigned int, comarg_t, void**, size_t*);
static int handle_to_fsfd(void *, char **);
+static char *path_to_fspath(char *path);
/*
@@ -70,13 +72,18 @@ path_to_fshandle(
comarg_t obj;
struct fdhash *fdhp;
char *tmppath;
+ char *fspath;
- fd = open(path, O_RDONLY);
+ fspath = path_to_fspath(path);
+ if (fspath == NULL)
+ return -1;
+
+ fd = open(fspath, O_RDONLY);
if (fd < 0)
return -1;
obj.path = path;
- result = obj_to_handle(path, fd, XFS_IOC_PATH_TO_FSHANDLE,
+ result = obj_to_handle(fspath, fd, XFS_IOC_PATH_TO_FSHANDLE,
obj, fshanp, fshlen);
if (result < 0) {
close(fd);
@@ -95,7 +102,7 @@ path_to_fshandle(
}
fdhp->fsfd = fd;
- strncpy(fdhp->fspath, path, sizeof(fdhp->fspath));
+ strncpy(fdhp->fspath, fspath, sizeof(fdhp->fspath));
memcpy(fdhp->fsh, *fshanp, FSIDSIZE);
fdhp->fnxt = fdhash_head;
@@ -114,18 +121,46 @@ path_to_handle(
int fd;
int result;
comarg_t obj;
+ char *fspath;
- fd = open(path, O_RDONLY);
+ fspath = path_to_fspath(path);
+ if (fspath == NULL)
+ return -1;
+
+ fd = open(fspath, O_RDONLY);
if (fd < 0)
return -1;
obj.path = path;
- result = obj_to_handle(path, fd, XFS_IOC_PATH_TO_HANDLE,
+ result = obj_to_handle(fspath, fd, XFS_IOC_PATH_TO_HANDLE,
obj, hanp, hlen);
close(fd);
return result;
}
+/* Given a path, return a suitable "fspath" for use in obtaining
+ * an fd for xfsctl calls. For regular files and directories the
+ * input path is sufficient. For other types the parent directory
+ * is used to avoid issues with opening dangling symlinks and
+ * potentially blocking in an open on a named pipe. Also
+ * symlinks to files on other filesystems would be a problem,
+ * since an fd would be obtained for the wrong fs.
+ */
+static char *
+path_to_fspath(char *path)
+{
+ static char dirpath[MAXPATHLEN];
+ struct stat statbuf;
+
+ if (lstat(path, &statbuf) != 0)
+ return NULL;
+
+ if (S_ISREG(statbuf.st_mode) || S_ISDIR(statbuf.st_mode))
+ return path;
+
+ strcpy(dirpath, path);
+ return dirname(dirpath);
+}
int
fd_to_handle (
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-23 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 16:52 [PATCH 1/2] add lpath_to_handle to libhandle Bill Kendall
2009-10-23 18:08 ` Alex Elder
2009-10-24 13:37 ` Christoph Hellwig
2009-10-25 2:52 ` Christoph Hellwig
2009-10-24 13:39 ` Christoph Hellwig
2009-12-21 23:56 ` Bill Kendall
2009-12-23 13:15 ` Christoph Hellwig
2009-12-23 19:21 ` Bill Kendall [this message]
2010-01-06 17:41 ` Christoph Hellwig
2009-10-25 3:44 ` Christoph Hellwig
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=20091223192101.GA3578@sgi.com \
--to=wkendall@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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