9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] copying over 9P using plan9port
Date: Tue,  4 Oct 2011 21:51:18 +0200	[thread overview]
Message-ID: <CAK8RtFoYL=HWJNe7r5BZhzvpZ63jcxQ0Vf7_5AwuaoW6u1dhTA@mail.gmail.com> (raw)
In-Reply-To: <CADSkJJUqbZSPnep+jKJFD7anL_5Ctyebu2fz8Bf4Rw7G3p2_Jw@mail.gmail.com>

2011/10/4 Russ Cox <rsc@swtch.com>:
> To answer my question: the error message comes from 9pfuse.
> The extra bits are O_NOFOLLOW and O_LARGEFILE, both of
> which seem harmless in this context.  Try this:
>
>
> diff -r 6db8fc2588f6 src/cmd/9pfuse/main.c
> --- a/src/cmd/9pfuse/main.c     Mon Oct 03 18:16:09 2011 -0400
> +++ b/src/cmd/9pfuse/main.c     Tue Oct 04 15:43:16 2011 -0400
> @@ -577,6 +577,13 @@
>        openmode = flags&3;
>        flags &= ~3;
>        flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE|O_CLOEXEC);
> +#ifdef O_NOFOLLOW
> +       flags &= ~O_NOFOLLOW
> +#endif
> +#ifdef O_LARGEFILE
> +       flags &= ~O_LARGEFILE
> +#endif
> +
>        /*
>         * Discarding O_APPEND here is not completely wrong,
>         * because the host kernel will rewrite the offsets
> @@ -594,7 +601,7 @@
>         *      O_NONBLOCK -> ONONBLOCK
>         */
>        if(flags){
> -               fprint(2, "unexpected open flags %#uo", (uint)in->flags);
> +               fprint(2, "unexpected open flags %#uo\n", (uint)in->flags);
>                replyfuseerrno(m, EACCES);
>                return;
>        }
>
>

Thanks I will try the patch as soon as I got time.

@ brian:

doing "cp -r" instead of "cp -ar" did not make a difference



  reply	other threads:[~2011-10-04 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 17:08 Jens Staal
2011-10-04 18:09 ` David du Colombier
2011-10-04 19:07   ` Jens Staal
2011-10-04 19:16 ` Russ Cox
2011-10-04 19:46   ` Jens Staal
2011-10-04 19:39 ` Brian L. Stuart
2011-10-04 19:44   ` Russ Cox
2011-10-04 19:51     ` Jens Staal [this message]
2011-10-05 15:08 ` Nicolas Bercher

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='CAK8RtFoYL=HWJNe7r5BZhzvpZ63jcxQ0Vf7_5AwuaoW6u1dhTA@mail.gmail.com' \
    --to=staal1978@gmail.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).