search for: s_type

...nux 6.0, 6.1, ... and try to check if it can be reproduced. I've tried trace mntget/mntput using the following bpftrace script, link-cp output shows it misses a fput. #include <linux/mount.h> #include <linux/string.h> kprobe:mntget { $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; if (!strncmp(str($n), "ocfs2", 5)) { @[comm] += 1; printf("%s", kstack); } } kprobe:mntput { $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; if (!strncmp(str($n), "ocfs2", 5)) { @[comm] +=1; printf("%s", kstack); } }...

...the following bpftrace script, >>> link-cp output shows it misses a fput. >>> >>> #include <linux/mount.h> >>> #include <linux/string.h> >>> >>> kprobe:mntget >>> { >>> $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; >>> >>> if (!strncmp(str($n), "ocfs2", 5)) { >>> @[comm] += 1; >>> >>> printf("%s", kstack); >>> } >>> } >>> >>> kprobe:mntput >>> { >>> $n = ((struct vfsmount *)a...

...ch time. > > I've tried trace mntget/mntput using the following bpftrace script, > link-cp output shows it misses a fput. > > #include <linux/mount.h> > #include <linux/string.h> > > kprobe:mntget > { > $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; > > if (!strncmp(str($n), "ocfs2", 5)) { > @[comm] += 1; > > printf("%s", kstack); > } > } > > kprobe:mntput > { > $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; > > if (!strncmp(str($n), "ocfs2&qu...

...ace mntget/mntput using the following bpftrace script, > > link-cp output shows it misses a fput. > > > > #include <linux/mount.h> > > #include <linux/string.h> > > > > kprobe:mntget > > { > > $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; > > > > if (!strncmp(str($n), "ocfs2", 5)) { > > @[comm] += 1; > > > > printf("%s", kstack); > > } > > } > > > > kprobe:mntput > > { > > $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->na...

...gt;>>> link-cp output shows it misses a fput. >>>> >>>> #include <linux/mount.h> >>>> #include <linux/string.h> >>>> >>>> kprobe:mntget >>>> { >>>> $n = ((struct vfsmount *)arg0)->mnt_sb->s_type->name; >>>> >>>> if (!strncmp(str($n), "ocfs2", 5)) { >>>> @[comm] += 1; >>>> >>>> printf("%s", kstack); >>>> } >>>> } >>>> >>>> kprobe:mntput >>>> {...

I'm running a bit late with the e-mail this time around, but I think that's ok since there really isn't any major new features here - the bulk of the Ocfs2 update is bug fixes, or cleanups. The same goes for configfs. The only two things that could be described as features would be: - Sunil has updated Ocfs2 to provide even more live cluster locking information via debugfs. - Joel

On 2/24/23 3:52 PM, Joseph Qi wrote: > > > On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: >> On 2/24/23 2:54 PM, Joseph Qi wrote: >>> I can reproduce this in my local VM. >>> I've traced ocfs2_dismount_volume and found that it hasn't been called. >>> So EBUSY is returned in VFS layer. I guess something wrong when doing >>> a copy

....append(" .get = (getter)py_%s_%s_get, "%(ty.rawname, f.name)) + l.append(" .set = (setter)py_%s_%s_set },"%(ty.rawname, f.name)) + l.append(" { .name = NULL }") + l.append("};") + struct=""" +static PyTypeObject Py%s_Type= { + PyObject_HEAD_INIT(NULL) + 0, + PKG ".%s", + sizeof(Py_%s), + 0, + (destructor)Py%s_dealloc, /* tp_dealloc */ + NULL, /* tp_print */ + NULL, /* tp_getattr */ + NULL,...

...t help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(sk_lock-AF_VSOCK); lock(sk_lock-AF_VSOCK); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by python3/872: #0: ffff88802c957180 (&sb->s_type->i_mutex_key#8){+.+.}, at: __sock_release+0x2d/0xb0 #1: ffff88803597ce10 (sk_lock-AF_VSOCK){+.+.}, at: __vsock_release+0x3f/0x130 [vsock] stack backtrace: CPU: 0 PID: 872 Comm: python3 Not tainted 5.3.0-vsock #17 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12....

...y holding lock: [ 1998.329940] (&(&eb->lock)->rlock){+.+...}, at: [<ffffffffa025dbae>] btrfs_clear_lock_blocking+0x22/0x2b [btrfs] [ 1998.478275] [ 1998.478275] other info that might help us debug this: [ 1998.478275] 2 locks held by dd/25718: [ 1998.478275] #0: (&sb->s_type->i_mutex_key#13){+.+.+.}, at: [<ffffffffa0240d97>] btrfs_file_aio_write+0xdc/0x49a [btrfs] [ 1998.478275] #1: (&(&eb->lock)->rlock){+.+...}, at: [<ffffffffa025dbae>] btrfs_clear_lock_blocking+0x22/0x2b [btrfs] [ 1998.478275] [ 1998.478275] stack backtrace: [ 1998.478...

Hi, the first four patches in this series fix locking problems in OCFS2 quota code (three of them can lead to potential deadlocks). The fifth patch reorders ip_alloc_sem for directories to be acquired before localalloc locks. Mark would you please merge these? The last two patches implement lockdep annotations for OCFS2 cluster locks. We annotate all the cluster locks except for special ones

...ossible unsafe locking scenario: > > CPU0 > ---- > lock(sk_lock-AF_VSOCK); > lock(sk_lock-AF_VSOCK); > > *** DEADLOCK *** > > May be due to missing lock nesting notation > > 2 locks held by server/1795: > #0: ffff8880c5d05ff8 (&sb->s_type->i_mutex_key#10){+.+.}, at: __sock_release+0x2d/0xa0 > #1: ffff8880c5158150 (sk_lock-AF_VSOCK){+.+.}, at: __vsock_release+0x2e/0xf0 [vsock] > > stack backtrace: > CPU: 5 PID: 1795 Comm: server Not tainted 5.3.0+ #1 > Call Trace: > dump_stack+0x67/0x90 > __lock_acquire.co...

...ossible unsafe locking scenario: > > CPU0 > ---- > lock(sk_lock-AF_VSOCK); > lock(sk_lock-AF_VSOCK); > > *** DEADLOCK *** > > May be due to missing lock nesting notation > > 2 locks held by server/1795: > #0: ffff8880c5d05ff8 (&sb->s_type->i_mutex_key#10){+.+.}, at: __sock_release+0x2d/0xa0 > #1: ffff8880c5158150 (sk_lock-AF_VSOCK){+.+.}, at: __vsock_release+0x2e/0xf0 [vsock] > > stack backtrace: > CPU: 5 PID: 1795 Comm: server Not tainted 5.3.0+ #1 > Call Trace: > dump_stack+0x67/0x90 > __lock_acquire.co...

...fff80299edf>] alloc_fd+0x106/0x117 [<ffffffff802857f6>] do_sys_open+0x48/0xcc [<ffffffff8020be5b>] system_call_fastpath+0x16/0x1b [<ffffffffffffffff>] 0xffffffffffffffff other info that might help us debug this: 3 locks held by cp/3919: #0: (&sb->s_type->i_mutex_key#13){--..}, at: [<ffffffff802916c6>] do_filp_open+0x153/0x806 #1: (Meta){----}, at: [<ffffffffa0307bde>] ocfs2_mknod+0x128/0xc42 [ocfs2] #2: (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){--..}, at: [<ffffffffa03017ff>] ocfs2_reserve_local_alloc_bits+...

...le *ddiag,int *idiag,double *sdiag, int *direct_mesh,double *min_edf,double *gcvubre,double *target_edf, double *hat); void RGAMsetup(double *Xd,double *Cd,double *Sd,double *UZd,double *Xud,int *xu,double *xpd, int *offd,double *xd,int *md,int *nd,int *dfd,int *nsdfd,int *dim,int *s_type, int *p_order, int *by_exists, double *byd,double *knots, int *n_knots); -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]su...

I already did what you said,please see the log results in zaptel.rar attached when I compile zapltel using make ********************************************* No employee or agent is authorized to conclude any binding agreement on behalf of Xplorium with another party by e-mail without express written confirmation by an officer of Xplorium. Any views expressed by an individual in this

Hi, here comes the next version of OCFS2 lockdep support. I've dropped patches with fixes from the series since they were already merged. As Joel suggested, I've simplified the main patch a bit so that we don't have ifdefs around lock declarations and there are also a few other minor improvements. Honza

I am using centos 4.4 server cd ,when I am trying to compile zaptel 1.4.2 ... error appears > >From where I can get the missing rpms .or kernel source >From where I can get the centos 4.4 server kernel source. Regards ********************************************* No employee or agent is authorized to conclude any binding agreement on behalf of Xplorium with another

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid

Hi, I'm resending this patch series. It's rediffed against linux-next branch of Joel's git tree. The first four patches are obvious fixes of deadlocks in quota code and should go in as soon as possible. The other three patches implement lockdep support for OCFS2 cluster locks. So you can have a look whether the code make sence to you and possibly merge them. They should be NOP when