9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pavel Zholkover <paulzhol@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ARM 9pfuse broken?
Date: Thu, 22 Mar 2012 20:30:47 +0200	[thread overview]
Message-ID: <CAJdW5jdGs==W9eZhim71SuruR7LCd5HFn3p5gf0szhVKs+EzWg@mail.gmail.com> (raw)
In-Reply-To: <86haxgtwgi.fsf@cmarib.ramside>

I've also encountered this on my synology DS411 linux based kirkwood
NAS. If I remember correctly I saw a comment by Russ regarding
weird/unhandled flags being passed to the open syscall.

My workaround was just to compile a 9p kernel module and mount the
vacfs export with it.

On Thu, Mar 22, 2012 at 6:46 PM,  <smiley@icebubble.org> wrote:
> Hello,
>
> Are there any known bugs in 9pfuse on ARM?  I can mount a vac file
> system OK with it, but trying to list files on it causes:
>
>  unexpected open flags 02444000
>  ls: cannot open directory /mnt/foo: Permission denied
>
> Trying to read files:
>
>  unexpected open flags 0400000
>  cat: /mnt/foo/bar.txt: Permission denied
>
> But walk/statting seem to succeed OK.  I'm planning to debug a bit
> deeper, but figured I'd give a shout out, in case this bug is already
> known, and to see if there was already a patch for it floating around.
>
> This is an ARMv7 OMAP4 Cortex-A9, in case that's any clue.
>
> --
> +---------------------------------------------------------------+
> |Smiley       <smiley@icebubble.org>    PGP key ID:    BC549F8B |
> |Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
> +---------------------------------------------------------------+
>



  reply	other threads:[~2012-03-22 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 16:46 smiley
2012-03-22 18:30 ` Pavel Zholkover [this message]
2012-03-22 18:42   ` Pavel Zholkover

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='CAJdW5jdGs==W9eZhim71SuruR7LCd5HFn3p5gf0szhVKs+EzWg@mail.gmail.com' \
    --to=paulzhol@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).