From: Dave Chinner <david@fromorbit.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: make fsr use mntinfo when there is no mntent
Date: Wed, 28 Oct 2015 15:56:45 +1100 [thread overview]
Message-ID: <20151028045645.GQ19199@dastard> (raw)
In-Reply-To: <1445338883-7000-1-git-send-email-jtulak@redhat.com>
On Tue, Oct 20, 2015 at 01:01:23PM +0200, Jan Tulak wrote:
> I'm resubmitting this patch from my OS X set - it wasn't included with
> others, nor in the current for-next, and I didn't got any review/reply
> to this last iteration.
>
> So my guess is it fell under the sofa, forgotten... :-)
>
> .........
>
> UPDATE:
> - refactor ifdefs to platform_ functions
> - refactor also the other ifdef which I forgot to change before
> - (and rebase against current for-next)
>
> For what fsr needs, mntinfo can be used instead of mntent on some
> platforms. Exctract the platform-specific code to platform headers.
>
> Signed-off-by: Jan Tulak <jtulak@redhat.com>
Code structure looks good now, but build warnings on linux:
[CC] xfs_fsr.o
xfs_fsr.c: In function ¿find_mountpoint_check¿:
xfs_fsr.c:184:26: warning: passing argument 2 of ¿stat64¿ from incompatible pointer type
if (stat64(t->mnt_dir, &ms) < 0)
^
In file included from /usr/include/features.h:374:0,
from /usr/include/stdio.h:27,
from ../include/platform_defs.h:24,
from ../include/libxfs.h:23,
from xfs_fsr.c:19:
/usr/include/x86_64-linux-gnu/sys/stat.h:502:1: note: expected ¿struct stat64 *¿ but argument is of type ¿struct stat64 **¿
__NTH (stat64 (const char *__path, struct stat64 *__statbuf))
^
xfs_fsr.c:195:29: warning: passing argument 2 of ¿stat64¿ from incompatible pointer type
if (stat64(t->mnt_fsname, &ms) < 0)
^
In file included from /usr/include/features.h:374:0,
from /usr/include/stdio.h:27,
from ../include/platform_defs.h:24,
from ../include/libxfs.h:23,
from xfs_fsr.c:19:
/usr/include/x86_64-linux-gnu/sys/stat.h:502:1: note: expected ¿struct stat64 *¿ but argument is of type ¿struct stat64 **¿
__NTH (stat64 (const char *__path, struct stat64 *__statbuf))
^
xfs_fsr.c: In function ¿initallfs¿:
xfs_fsr.c:435:39: warning: passing argument 2 of ¿platform_mntent_next¿ from incompatible pointer type
while (platform_mntent_next(&cursor, &mp) == 0) {
^
In file included from ../include/xfs.h:37:0,
from ../include/libxfs.h:24,
from xfs_fsr.c:19:
../include/xfs/linux.h:166:19: note: expected ¿struct mntent *¿ but argument is of type ¿struct mntent **¿
static inline int platform_mntent_next(struct mntent_cursor * cursor, struct mntent * t)
^
xfs_fsr.c:436:37: warning: passing argument 2 of ¿find_mountpoint_check¿ from incompatible pointer type
mntp = find_mountpoint_check(&sb, &mp, &ms);
^
xfs_fsr.c:181:1: note: expected ¿struct mntent *¿ but argument is of type ¿struct mntent **¿
find_mountpoint_check(struct stat64 *sb, struct mntent *t, struct stat64 *ms)
^
[LD] libxcmd.la
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-10-28 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 11:01 [PATCH] xfsprogs: make fsr use mntinfo when there is no mntent Jan Tulak
2015-10-28 4:56 ` Dave Chinner [this message]
2015-10-29 15:26 ` [PATCH v2] " Jan Tulak
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=20151028045645.GQ19199@dastard \
--to=david@fromorbit.com \
--cc=jtulak@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.