Re: December 2024 stabilization week CANCELED!

2024-12-17 Thread Gleb Smirnoff
On Wed, Dec 18, 2024 at 08:29:46AM +0800, George Neville-Neil wrote: G> > due to shortage of human resources and due to reservation of certain hardware G> > for the Christmas events, we won't be able to properly A/B test the December G> > snapshot at Netflix as we usually do. Given that testing

Re: Why does namei return an exclusively locked vnode when LOCKSHARED is specified?

2024-12-17 Thread Alan Somers
On Tue, Dec 17, 2024 at 12:27 PM Mark Johnston wrote: > > On Tue, Dec 17, 2024 at 12:19:26PM -0700, Alan Somers wrote: > > According to namei(9), namei should return a shared lock when > > LOCKSHARED is specified. But in my experiments, it always seems to > > return an exclusive lock instead. Fo

Re: Why does namei return an exclusively locked vnode when LOCKSHARED is specified?

2024-12-17 Thread Mark Johnston
On Tue, Dec 17, 2024 at 12:19:26PM -0700, Alan Somers wrote: > According to namei(9), namei should return a shared lock when > LOCKSHARED is specified. But in my experiments, it always seems to > return an exclusive lock instead. For example: > > $ cd /usr/tests/sys/fs/fusefs > $ sudo dtrace -i

Why does namei return an exclusively locked vnode when LOCKSHARED is specified?

2024-12-17 Thread Alan Somers
According to namei(9), namei should return a shared lock when LOCKSHARED is specified. But in my experiments, it always seems to return an exclusive lock instead. For example: $ cd /usr/tests/sys/fs/fusefs $ sudo dtrace -i 'fbt:fusefs:fuse_vnop_getattr:entry /pid==$target/ {printf("islocked=%#x"