Re: new 9p kasan splat in 6.9

["Eric Van Hensbergen" <eric.vanhensbergen@linux.dev>]

April 1, 2024 at 8:12 PM, "Kent Overstreet" <kent.overstreet@linux.dev> wrote:
> 
> On Mon, Apr 01, 2024 at 07:33:50PM -0500, Eric Van Hensbergen wrote:
> 
> 
> Sounds like things were rushed a bit then, and there's some room for 
> improving the testing.
> 

Well, most of the patches had been in there almost since the last release, its just I didn't have time to test and incorporate fixes during the -rc cycle and most of the ones I saw looked like corner cases from kasan so I didn't give them as much attention as perhaps I should have.

> If you need testing automation I might be able to help.

I do like your dashboards and what not, not sure if I'm up for trying Nix again though ;)

> 
> > 
> > Looking at your example above -- is it the case that most of these,
> >  there is essentially a missing log file that isn't being created by
> >  9p?
> > 
> 
> Appears to be, but it doesn't happen often enough for me to repro
> locally.
> 

Okay, that's useful to see if I can track things down.

> > 
> > Any other details you can give me from your environment (how is
> > 
> >  9p mounted, is this qemu?, etc.)?
> > 
> 
> It's qemu, standard mount options:
> host /host 9p rw,relatime,access=client,trans=virtio 0 0
>

access=client may be someplace for me to start, I don't usually use ACL based checks in my regression sweeps.  I'll update to add that to the matrix as well as put fstest back in the default regressions.

trans=virtio,version=9p2000.L,cache=none,access=user

should still be the most stable, but this recent set of patches does change inode (and inode_no) handling and I believe by default they may stick around even though with nocache they should always be refreshed.

     -eric