search for: sys_fsetxattr

...xattr' lib/system.c: In function 'sys_fremovexattr': lib/system.c:1811: error: too few arguments to function 'fremovexattr' lib/system.c: In function 'sys_setxattr': lib/system.c:1842: error: too few arguments to function 'setxattr' lib/system.c: In function 'sys_fsetxattr': lib/system.c:1939: error: too few arguments to function 'fsetxattr' Since I am a C programmer, I looked at the prototype for getxattr. It is ssize_t getxattr(const char *path, const char *name, void *value, size_t size, u_int32_t position, int options); and in the lib/system.c, it i...

.../0x90 [<ffffffff81191670>] __vfs_setxattr_noperm+0x80/0x1a0 [<ffffffff81191839>] vfs_setxattr+0xa9/0xb0 [<ffffffff81191903>] setxattr+0xc3/0x120 [<ffffffff81061c40>] ? finish_task_switch+0x70/0xe0 [<ffffffff81505a54>] ? __schedule+0x364/0x6d0 [<ffffffff81191a08>] sys_fsetxattr+0xa8/0xd0 [<ffffffff81510642>] system_call_fastpath+0x16/0x1b Code: 0f 1f 40 00 eb ae 0f 0b eb fe 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 66 66 66 90 39 77 10 7e 09 48 8b 47 28 ff 50 10 c9 c3 <0f> 0b eb fe 0f 1f 44 00 00 55 48 89 e5 53 48 83 ec 08 66 66 66 RIP [<ffffffffa04cd19...

An user reported that he has hit an annoying deadlock while playing with ceph based on btrfs. Current updating device tree requires space from METADATA chunk, so we -may- need to do a recursive chunk allocation when adding/updating dev extent, that is where the deadlock comes from. If we use SYSTEM metadata to update device tree, we can avoid the recursive stuff. Reported-by: Jim Schutt