All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <eric.vanhensbergen@linux.dev>
To: "Itaru Kitayama" <itaru.kitayama@linux.dev>,
	"Dominique Martinet" <asmadeus@codewreck.org>
Cc: v9fs@lists.linux.dev
Subject: Re: ftruncate fails
Date: Tue, 16 Apr 2024 14:16:29 +0000	[thread overview]
Message-ID: <d7164a3abce2d194041d9179a9ef153d75edb099@linux.dev> (raw)
In-Reply-To: <74C91BF3-4BC7-46A7-9BB2-1360E07B6FE5@linux.dev>

Itaru,

If you can, could confirm that your issues go away with the pending-fixes branch of the next tree?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h=pending-fixes

I work for Arm as well, so if you could point me at the revision of FVP you are seeing the problems on I could also have a look at the server side of it and see if its breaking any assumptions we've been operating under using Qemu as our primary server.

     -eric


April 7, 2024 at 9:22 PM, "Itaru Kitayama" <itaru.kitayama@linux.dev> wrote:
> 
> > 
> > On Apr 8, 2024, at 11:08, Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> > 
> >  
> > 
> >  Hi,
> > 
> >  
> > 
> > > 
> > > On Apr 8, 2024, at 11:01, Dominique Martinet <asmadeus@codewreck.org> wrote:
> > > 
> > >  
> > > 
> > >  Itaru Kitayama wrote on Mon, Apr 08, 2024 at 10:44:51AM +0900:
> > > 
> > 
> >  With a recent kernel I see below program fails (Bus error) if executed
> > 
> >  from 9p mounted directory, not with the local filesystem (Ext4).
> > 
> > > 
> > > I cannot reproduce on 6.8/6.9-rc2 with qemu and a couple of options.
> > > 
> > >  Bus error would be some problem with the mmap of the executable given
> > > 
> > >  this code? so probably doesn't have anything to do with the content of
> > > 
> > >  the program itself...
> > > 
> > >  
> > > 
> > >  A few questions:
> > > 
> > >  - What exact kernel are you running? (or closest approximation)
> > > 
> > 
> >  
> > 
> >  v6.9-rc3
> > 
> >  
> > 
> > > 
> > > - What server? (assuming qemu) what mount option? (tried default
> > > 
> > >  cacheless and cache=loose)
> > > 
> > 
> >  
> > 
> >  FVP and just mount -t 9p FM /mnt
> > 
> >  
> > 
> > > 
> > > - Does this reproduce right after boot/mounting the 9p filesystem?
> > > 
> > 
> >  
> > 
> >  Not immediately after the boot/mounting.
> > 
> 
> My reproducer wasn’t explaining what a kselftests was showing.
> 
> If you build the “mm” subsystem and execute one of the programs, gup_longterm from the 9p mounted directory, you’ll notice the ftruncate error.
> 
> Thanks,
> 
> Itaru.
> 
> > 
> > Thanks,
> > 
> >  Itaru.
> > 
> >  
> > 
> > > 
> > > Thanks
> > > 
> > >  -- 
> > > 
> > >  Dominique Martinet | Asmadeus
> > >
> >
>

  parent reply	other threads:[~2024-04-16 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08  1:44 ftruncate fails Itaru Kitayama
2024-04-08  2:01 ` Dominique Martinet
2024-04-08  2:08   ` Itaru Kitayama
2024-04-08  2:22     ` Itaru Kitayama
2024-04-08  4:07       ` Dominique Martinet
2024-04-16 14:16       ` Eric Van Hensbergen [this message]
2024-04-12 20:36         ` Itaru Kitayama
2024-04-17  0:20           ` Eric Van Hensbergen
2024-04-17  0:25             ` Itaru Kitayama
2024-04-17  0:41               ` Eric Van Hensbergen

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=d7164a3abce2d194041d9179a9ef153d75edb099@linux.dev \
    --to=eric.vanhensbergen@linux.dev \
    --cc=asmadeus@codewreck.org \
    --cc=itaru.kitayama@linux.dev \
    --cc=v9fs@lists.linux.dev \
    /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.