2019-05-28 09:57:16 -07:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 17:04:11 +09:00
|
|
|
|
2017-02-08 18:51:30 +01:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
2024-03-18 20:29:53 +00:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2007-10-17 14:31:07 -05:00
|
|
|
|
2017-07-05 16:25:37 +01:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-13 18:45:25 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-08-07 00:46:59 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-28 00:38:36 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-09-04 17:07:12 +02:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 10:46:57 +01:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
|
|
|
|
|
2010-09-22 20:43:57 +00:00
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-22 20:43:57 +00:00
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-07-05 16:25:37 +01:00
|
|
|
|
|
|
|
|
|
2021-09-04 17:07:12 +02:00
|
|
|
|
2017-07-05 16:25:37 +01:00
|
|
|
|
2017-11-19 11:28:43 +02:00
|
|
|
|
2017-07-05 16:25:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2012-08-10 15:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2012-08-10 15:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2010-04-05 14:37:28 -05:00
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-08 17:33:04 +00:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2021-03-27 16:15:54 +08:00
|
|
|
|
2009-07-19 13:41:55 -06:00
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2010-02-08 16:23:23 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2013-05-20 12:20:54 +05:30
|
|
|
|
2021-09-04 17:07:12 +02:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-02-08 16:23:23 -06:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2010-02-08 16:23:23 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
2011-08-30 12:19:34 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-30 12:19:34 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
2018-11-05 09:52:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2018-04-05 16:20:01 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2010-01-15 19:01:10 -06:00
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2018-06-07 17:05:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-06 18:35:32 +05:30
|
|
|
|
2010-03-05 18:49:11 +00:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-24 16:22:23 -05:00
|
|
|
|
2010-01-15 19:01:10 -06:00
|
|
|
|
2018-07-13 16:59:06 -07:00
|
|
|
|
|
|
|
|
|
2010-02-08 16:23:23 -06:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
|
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
|
|
|
|
|
2013-06-21 15:32:36 +02:00
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
2013-06-21 15:32:36 +02:00
|
|
|
|
2024-04-08 07:10:39 -07:00
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2013-06-21 15:32:36 +02:00
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2021-03-27 16:15:54 +08:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2011-08-26 19:57:40 +03:00
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-09-26 13:39:34 +03:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2022-07-15 23:32:28 +02:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-15 23:32:28 +02:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
2019-06-13 15:08:54 +08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
9p: set req refcount to zero to avoid uninitialized usage
When a new request is allocated, the refcount will be zero if it is
reused, but if the request is newly allocated from slab, it is not fully
initialized before being added to idr.
If the p9_read_work got a response before the refcount initiated. It will
use a uninitialized req, which will result in a bad request data struct.
Here is the logs from syzbot.
Corrupted memory at 0xffff88807eade00b [ 0xff 0x07 0x00 0x00 0x00 0x00
0x00 0x00 . . . . . . . . ] (in kfence-#110):
p9_fcall_fini net/9p/client.c:248 [inline]
p9_req_put net/9p/client.c:396 [inline]
p9_req_put+0x208/0x250 net/9p/client.c:390
p9_client_walk+0x247/0x540 net/9p/client.c:1165
clone_fid fs/9p/fid.h:21 [inline]
v9fs_fid_xattr_set+0xe4/0x2b0 fs/9p/xattr.c:118
v9fs_xattr_set fs/9p/xattr.c:100 [inline]
v9fs_xattr_handler_set+0x6f/0x120 fs/9p/xattr.c:159
__vfs_setxattr+0x119/0x180 fs/xattr.c:182
__vfs_setxattr_noperm+0x129/0x5f0 fs/xattr.c:216
__vfs_setxattr_locked+0x1d3/0x260 fs/xattr.c:277
vfs_setxattr+0x143/0x340 fs/xattr.c:309
setxattr+0x146/0x160 fs/xattr.c:617
path_setxattr+0x197/0x1c0 fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__ia32_sys_setxattr+0xc0/0x160 fs/xattr.c:648
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178
do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203
entry_SYSENTER_compat_after_hwframe+0x70/0x82
Below is a similar scenario, the scenario in the syzbot log looks more
complicated than this one, but this patch can fix it.
T21124 p9_read_work
======================== second trans =================================
p9_client_walk
p9_client_rpc
p9_client_prepare_req
p9_tag_alloc
req = kmem_cache_alloc(p9_req_cache, GFP_NOFS);
tag = idr_alloc
<< preempted >>
req->tc.tag = tag;
/* req->[refcount/tag] == uninitialized */
m->rreq = p9_tag_lookup(m->client, m->rc.tag);
/* increments uninitalized refcount */
refcount_set(&req->refcount, 2);
/* cb drops one ref */
p9_client_cb(req)
/* reader thread drops its ref:
request is incorrectly freed */
p9_req_put(req)
/* use after free and ref underflow */
p9_req_put(req)
To fix it, we can initialize the refcount to zero before add to idr.
Link: https://lkml.kernel.org/r/20221201033310.18589-1-schspa@gmail.com
Cc: stable@vger.kernel.org # 6.0+ due to 6cda12864cb0 ("9p: Drop kref usage")
Fixes: 728356dedeff ("9p: Add refcount to p9_req_t")
Reported-by: syzbot+8f1060e2aaf8ca55220b@syzkaller.appspotmail.com
Signed-off-by: Schspa Shi <schspa@gmail.com>
Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
2022-12-01 11:33:10 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-03 21:02:49 -04:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2013-06-21 15:32:34 +02:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2013-06-21 15:32:34 +02:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-03 21:08:18 -04:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-11 16:42:53 +02:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-08-11 16:42:53 +02:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
2022-07-03 21:08:18 -04:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2022-07-03 21:02:49 -04:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2022-07-03 21:02:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
2009-07-19 13:41:55 -06:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:22 -05:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
2020-10-31 19:26:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
2014-01-17 18:31:00 +01:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2014-01-17 18:31:00 +01:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2018-07-11 14:02:20 -07:00
|
|
|
|
2014-01-17 18:31:00 +01:00
|
|
|
|
|
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2014-01-17 18:31:00 +01:00
|
|
|
|
2018-07-11 14:02:23 -07:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-03 21:08:18 -04:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-23 17:44:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-11-22 20:20:29 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-23 17:44:04 +02:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-07 00:46:59 +05:30
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
2023-10-27 11:03:02 +08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2023-10-27 11:03:02 +08:00
|
|
|
|
|
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
2023-10-27 11:03:02 +08:00
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
remove lots of IS_ERR_VALUE abuses
Most users of IS_ERR_VALUE() in the kernel are wrong, as they
pass an 'int' into a function that takes an 'unsigned long'
argument. This happens to work because the type is sign-extended
on 64-bit architectures before it gets converted into an
unsigned type.
However, anything that passes an 'unsigned short' or 'unsigned int'
argument into IS_ERR_VALUE() is guaranteed to be broken, as are
8-bit integers and types that are wider than 'unsigned long'.
Andrzej Hajda has already fixed a lot of the worst abusers that
were causing actual bugs, but it would be nice to prevent any
users that are not passing 'unsigned long' arguments.
This patch changes all users of IS_ERR_VALUE() that I could find
on 32-bit ARM randconfig builds and x86 allmodconfig. For the
moment, this doesn't change the definition of IS_ERR_VALUE()
because there are probably still architecture specific users
elsewhere.
Almost all the warnings I got are for files that are better off
using 'if (err)' or 'if (err < 0)'.
The only legitimate user I could find that we get a warning for
is the (32-bit only) freescale fman driver, so I did not remove
the IS_ERR_VALUE() there but changed the type to 'unsigned long'.
For 9pfs, I just worked around one user whose calling conventions
are so obscure that I did not dare change the behavior.
I was using this definition for testing:
#define IS_ERR_VALUE(x) ((unsigned long*)NULL == (typeof (x)*)NULL && \
unlikely((unsigned long long)(x) >= (unsigned long long)(typeof(x))-MAX_ERRNO))
which ends up making all 16-bit or wider types work correctly with
the most plausible interpretation of what IS_ERR_VALUE() was supposed
to return according to its users, but also causes a compile-time
warning for any users that do not pass an 'unsigned long' argument.
I suggested this approach earlier this year, but back then we ended
up deciding to just fix the users that are obviously broken. After
the initial warning that caused me to get involved in the discussion
(fs/gfs2/dir.c) showed up again in the mainline kernel, Linus
asked me to send the whole thing again.
[ Updated the 9p parts as per Al Viro - Linus ]
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Andrzej Hajda <a.hajda@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: https://lkml.org/lkml/2016/1/7/363
Link: https://lkml.org/lkml/2016/5/27/486
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> # For nvmem part
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-05-27 23:23:25 +02:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
remove lots of IS_ERR_VALUE abuses
Most users of IS_ERR_VALUE() in the kernel are wrong, as they
pass an 'int' into a function that takes an 'unsigned long'
argument. This happens to work because the type is sign-extended
on 64-bit architectures before it gets converted into an
unsigned type.
However, anything that passes an 'unsigned short' or 'unsigned int'
argument into IS_ERR_VALUE() is guaranteed to be broken, as are
8-bit integers and types that are wider than 'unsigned long'.
Andrzej Hajda has already fixed a lot of the worst abusers that
were causing actual bugs, but it would be nice to prevent any
users that are not passing 'unsigned long' arguments.
This patch changes all users of IS_ERR_VALUE() that I could find
on 32-bit ARM randconfig builds and x86 allmodconfig. For the
moment, this doesn't change the definition of IS_ERR_VALUE()
because there are probably still architecture specific users
elsewhere.
Almost all the warnings I got are for files that are better off
using 'if (err)' or 'if (err < 0)'.
The only legitimate user I could find that we get a warning for
is the (32-bit only) freescale fman driver, so I did not remove
the IS_ERR_VALUE() there but changed the type to 'unsigned long'.
For 9pfs, I just worked around one user whose calling conventions
are so obscure that I did not dare change the behavior.
I was using this definition for testing:
#define IS_ERR_VALUE(x) ((unsigned long*)NULL == (typeof (x)*)NULL && \
unlikely((unsigned long long)(x) >= (unsigned long long)(typeof(x))-MAX_ERRNO))
which ends up making all 16-bit or wider types work correctly with
the most plausible interpretation of what IS_ERR_VALUE() was supposed
to return according to its users, but also causes a compile-time
warning for any users that do not pass an 'unsigned long' argument.
I suggested this approach earlier this year, but back then we ended
up deciding to just fix the users that are obviously broken. After
the initial warning that caused me to get involved in the discussion
(fs/gfs2/dir.c) showed up again in the mainline kernel, Linus
asked me to send the whole thing again.
[ Updated the 9p parts as per Al Viro - Linus ]
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Andrzej Hajda <a.hajda@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: https://lkml.org/lkml/2016/1/7/363
Link: https://lkml.org/lkml/2016/5/27/486
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> # For nvmem part
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-05-27 23:23:25 +02:00
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2010-07-28 14:17:26 +05:30
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2021-11-02 19:47:47 +09:00
|
|
|
|
|
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-02-01 20:04:59 -08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2010-07-28 14:17:26 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-07-28 14:17:26 +05:30
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2011-05-08 18:46:38 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2009-07-19 13:41:55 -06:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-05-08 18:46:38 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2013-07-25 10:54:24 +02:00
|
|
|
|
2013-06-21 15:32:42 +02:00
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2014-03-10 16:38:49 +01:00
|
|
|
|
|
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2009-04-05 16:28:59 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-07-15 23:32:28 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2022-07-03 21:08:18 -04:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-07-15 23:33:56 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2022-11-22 20:20:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2022-07-03 21:08:18 -04:00
|
|
|
|
2011-04-15 13:59:33 +05:30
|
|
|
|
2010-09-29 18:33:41 -07:00
|
|
|
|
net/9p: avoid -ERESTARTSYS leak to userspace
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clears TIF_SIGPENDING, handles
the request and calls recalc_sigpending() before returning.
Unfortunately, if the transmission of this cleanup request fails for any
reason, the transport returns an error and the client propagates it
right away, without calling recalc_sigpending().
This ends up with -ERESTARTSYS from the initially interrupted request
crawling up to syscall exit, with TIF_SIGPENDING cleared by the cleanup
request. The specific signal handling code, which is responsible for
converting -ERESTARTSYS to -EINTR is not called, and userspace receives
the confusing errno value:
open: Unknown error 512 (512)
This is really hard to hit in real life. I discovered the issue while
working on hot-unplug of a virtio-9p-pci device with an instrumented
QEMU allowing to control request completion.
Both p9_client_zc_rpc() and p9_client_rpc() functions have this buggy
error path actually. Their code flow is a bit obscure and the best
thing to do would probably be a full rewrite: to really ensure this
situation of clearing TIF_SIGPENDING and returning -ERESTARTSYS can
never happen.
But given the general lack of interest for the 9p code, I won't risk
breaking more things. So this patch simply fixes the buggy paths in
both functions with a trivial label+goto.
Thanks to Laurent Dufour for his help and suggestions on how to find the
root cause and how to fix it.
Link: http://lkml.kernel.org/r/152062809886.10599.7361006774123053312.stgit@bahia.lan
Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Yiwen Jiang <jiangyiwen@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>
Cc: Ron Minnich <rminnich@sandia.gov>
Cc: Latchesar Ionkov <lucho@ionkov.net>
Cc: David Miller <davem@davemloft.net>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-04-05 16:19:44 -07:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2012-02-01 12:48:53 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2014-01-17 18:31:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2012-02-01 12:48:53 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-05 16:28:59 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2009-04-05 16:28:59 -05:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
net/9p: avoid -ERESTARTSYS leak to userspace
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clears TIF_SIGPENDING, handles
the request and calls recalc_sigpending() before returning.
Unfortunately, if the transmission of this cleanup request fails for any
reason, the transport returns an error and the client propagates it
right away, without calling recalc_sigpending().
This ends up with -ERESTARTSYS from the initially interrupted request
crawling up to syscall exit, with TIF_SIGPENDING cleared by the cleanup
request. The specific signal handling code, which is responsible for
converting -ERESTARTSYS to -EINTR is not called, and userspace receives
the confusing errno value:
open: Unknown error 512 (512)
This is really hard to hit in real life. I discovered the issue while
working on hot-unplug of a virtio-9p-pci device with an instrumented
QEMU allowing to control request completion.
Both p9_client_zc_rpc() and p9_client_rpc() functions have this buggy
error path actually. Their code flow is a bit obscure and the best
thing to do would probably be a full rewrite: to really ensure this
situation of clearing TIF_SIGPENDING and returning -ERESTARTSYS can
never happen.
But given the general lack of interest for the 9p code, I won't risk
breaking more things. So this patch simply fixes the buggy paths in
both functions with a trivial label+goto.
Thanks to Laurent Dufour for his help and suggestions on how to find the
root cause and how to fix it.
Link: http://lkml.kernel.org/r/152062809886.10599.7361006774123053312.stgit@bahia.lan
Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Yiwen Jiang <jiangyiwen@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>
Cc: Ron Minnich <rminnich@sandia.gov>
Cc: Latchesar Ionkov <lucho@ionkov.net>
Cc: David Miller <davem@davemloft.net>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-04-05 16:19:44 -07:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2011-08-07 00:46:59 +05:30
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2012-08-10 15:52:06 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2020-07-13 01:14:57 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2022-07-15 23:32:28 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-22 20:20:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-04 16:04:19 -04:00
|
|
|
|
net/9p: avoid -ERESTARTSYS leak to userspace
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clears TIF_SIGPENDING, handles
the request and calls recalc_sigpending() before returning.
Unfortunately, if the transmission of this cleanup request fails for any
reason, the transport returns an error and the client propagates it
right away, without calling recalc_sigpending().
This ends up with -ERESTARTSYS from the initially interrupted request
crawling up to syscall exit, with TIF_SIGPENDING cleared by the cleanup
request. The specific signal handling code, which is responsible for
converting -ERESTARTSYS to -EINTR is not called, and userspace receives
the confusing errno value:
open: Unknown error 512 (512)
This is really hard to hit in real life. I discovered the issue while
working on hot-unplug of a virtio-9p-pci device with an instrumented
QEMU allowing to control request completion.
Both p9_client_zc_rpc() and p9_client_rpc() functions have this buggy
error path actually. Their code flow is a bit obscure and the best
thing to do would probably be a full rewrite: to really ensure this
situation of clearing TIF_SIGPENDING and returning -ERESTARTSYS can
never happen.
But given the general lack of interest for the 9p code, I won't risk
breaking more things. So this patch simply fixes the buggy paths in
both functions with a trivial label+goto.
Thanks to Laurent Dufour for his help and suggestions on how to find the
root cause and how to fix it.
Link: http://lkml.kernel.org/r/152062809886.10599.7361006774123053312.stgit@bahia.lan
Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Yiwen Jiang <jiangyiwen@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>
Cc: Ron Minnich <rminnich@sandia.gov>
Cc: Latchesar Ionkov <lucho@ionkov.net>
Cc: David Miller <davem@davemloft.net>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-04-05 16:19:44 -07:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-05 21:39:01 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
net/9p: avoid -ERESTARTSYS leak to userspace
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clears TIF_SIGPENDING, handles
the request and calls recalc_sigpending() before returning.
Unfortunately, if the transmission of this cleanup request fails for any
reason, the transport returns an error and the client propagates it
right away, without calling recalc_sigpending().
This ends up with -ERESTARTSYS from the initially interrupted request
crawling up to syscall exit, with TIF_SIGPENDING cleared by the cleanup
request. The specific signal handling code, which is responsible for
converting -ERESTARTSYS to -EINTR is not called, and userspace receives
the confusing errno value:
open: Unknown error 512 (512)
This is really hard to hit in real life. I discovered the issue while
working on hot-unplug of a virtio-9p-pci device with an instrumented
QEMU allowing to control request completion.
Both p9_client_zc_rpc() and p9_client_rpc() functions have this buggy
error path actually. Their code flow is a bit obscure and the best
thing to do would probably be a full rewrite: to really ensure this
situation of clearing TIF_SIGPENDING and returning -ERESTARTSYS can
never happen.
But given the general lack of interest for the 9p code, I won't risk
breaking more things. So this patch simply fixes the buggy paths in
both functions with a trivial label+goto.
Thanks to Laurent Dufour for his help and suggestions on how to find the
root cause and how to fix it.
Link: http://lkml.kernel.org/r/152062809886.10599.7361006774123053312.stgit@bahia.lan
Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Yiwen Jiang <jiangyiwen@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>
Cc: Ron Minnich <rminnich@sandia.gov>
Cc: Latchesar Ionkov <lucho@ionkov.net>
Cc: David Miller <davem@davemloft.net>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2018-04-05 16:19:44 -07:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: handling Rerror without copy_from_iter_full()
p9_client_zc_rpc()/p9_check_zc_errors() are playing fast
and loose with copy_from_iter_full().
Reading from file is done by sending Tread request. Response
consists of fixed-sized header (including the amount of data actually
read) followed by the data itself.
For zero-copy case we arrange the things so that the first
11 bytes of reply go into the fixed-sized buffer, with the rest going
straight into the pages we want to read into.
What makes the things inconvenient is that sglist describing
what should go where has to be set *before* the reply arrives. As
the result, if reply is an error, the things get interesting. On success
we get
size[4] Rread tag[2] count[4] data[count]
For error layout varies depending upon the protocol variant -
in original 9P and 9P2000 it's
size[4] Rerror tag[2] len[2] error[len]
in 9P2000.U
size[4] Rerror tag[2] len[2] error[len] errno[4]
in 9P2000.L
size[4] Rlerror tag[2] errno[4]
The last case is nice and simple - we have an 11-byte response
that fits into the fixed-sized buffer we hoped to get an Rread into.
In other two, though, we get a variable-length string spill into the
pages we'd prepared for the data to be read.
Had that been in fixed-sized buffer (which is actually 4K),
we would've dealt with that the same way we handle non-zerocopy case.
However, for zerocopy it doesn't end up there, so we need to copy it
from those pages.
The trouble is, by the time we get around to that, the
references to pages in question are already dropped. As the result,
p9_zc_check_errors() tries to get the data using copy_from_iter_full().
Unfortunately, the iov_iter it's trying to read from might *NOT* be
capable of that. It is, after all, a data destination, not data source.
In particular, if it's an ITER_PIPE one, copy_from_iter_full() will
simply fail.
In ->zc_request() itself we do have those pages and dealing with
the problem in there would be a simple matter of memcpy_from_page()
into the fixed-sized buffer. Moreover, it isn't hard to recognize
the (rare) case when such copying is needed. That way we get rid of
p9_zc_check_errors() entirely - p9_check_errors() can be used instead
both for zero-copy and non-zero-copy cases.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2022-06-09 10:01:34 -04:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2011-08-07 00:46:59 +05:30
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2012-08-10 15:52:06 +02:00
|
|
|
|
2008-10-13 18:45:21 -05:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
2008-10-28 14:22:43 -05:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
net/9p: Initialize the iounit field during fid creation
Ensure that the fid's iounit field is set to zero when a new fid is
created. Certain 9P operations, such as OPEN and CREATE, allow the
server to reply with an iounit size which the client code assigns to the
p9_fid struct shortly after the fid is created by p9_fid_create(). On
the other hand, an XATTRWALK operation doesn't allow for the server to
specify an iounit value. The iounit field of the newly allocated p9_fid
struct remained uninitialized in that case. Depending on allocation
patterns, the iounit value could have been something reasonable that was
carried over from previously freed fids or, in the worst case, could
have been arbitrary values from non-fid related usages of the memory
location.
The bug was detected in the Windows Subsystem for Linux 2 (WSL2) kernel
after the uninitialized iounit field resulted in the typical sequence of
two getxattr(2) syscalls, one to get the size of an xattr and another
after allocating a sufficiently sized buffer to fit the xattr value, to
hit an unexpected ERANGE error in the second call to getxattr(2). An
uninitialized iounit field would sometimes force rsize to be smaller
than the xattr value size in p9_client_read_once() and the 9P server in
WSL refused to chunk up the READ on the attr_fid and, instead, returned
ERANGE to the client. The virtfs server in QEMU seems happy to chunk up
the READ and this problem goes undetected there.
Link: https://lkml.kernel.org/r/20220710141402.803295-1-tyhicks@linux.microsoft.com
Fixes: ebf46264a004 ("fs/9p: Add support user. xattr")
Cc: stable@vger.kernel.org
Signed-off-by: Tyler Hicks <tyhicks@linux.microsoft.com>
Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
2022-07-10 09:14:02 -05:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2018-07-11 14:02:21 -07:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
2008-11-14 10:38:44 +11:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2020-11-03 09:35:57 +01:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-13 08:32:06 +09:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
2022-06-13 08:32:06 +09:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:21 -07:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-23 16:31:02 -05:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2022-06-13 08:32:06 +09:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2008-10-23 16:31:02 -05:00
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
2008-10-23 16:31:02 -05:00
|
|
|
|
2009-11-02 08:39:28 -06:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2022-06-13 08:32:06 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-19 06:48:16 +00:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2018-07-10 00:29:43 +02:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2010-03-05 18:51:04 +00:00
|
|
|
|
|
|
|
|
|
2010-03-08 17:33:04 +00:00
|
|
|
|
2010-03-05 18:51:04 +00:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-05 18:51:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-05 18:51:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-05 18:51:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-08 17:33:04 +00:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2018-11-05 09:52:48 +01:00
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-11-05 09:52:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-21 11:57:38 -07:00
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
2013-08-21 18:24:47 +01:00
|
|
|
|
2024-08-07 10:47:25 +01:00
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-24 16:22:23 -05:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
2013-08-21 18:24:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2008-03-07 10:53:53 -06:00
|
|
|
|
2009-07-14 13:24:10 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
2010-02-08 18:18:34 -06:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2008-10-13 18:45:25 -05:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2021-12-30 14:23:18 +01:00
|
|
|
|
2011-06-29 18:06:33 -07:00
|
|
|
|
2021-12-30 14:23:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-06 19:25:03 -06:00
|
|
|
|
2018-11-05 09:52:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-03-13 16:01:37 +08:00
|
|
|
|
2018-11-05 09:52:48 +01:00
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:14 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2010-02-08 18:18:34 -06:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2024-10-21 11:57:38 -07:00
|
|
|
|
|
|
|
|
|
2024-08-07 10:47:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-07 10:47:25 +01:00
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-07 10:47:25 +01:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2010-02-08 18:18:34 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-13 18:45:25 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-09-24 16:22:23 -05:00
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:22 -07:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2010-03-29 18:13:59 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-13 18:45:23 -05:00
|
|
|
|
|
|
|
|
|
2018-07-30 15:14:37 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-13 18:45:25 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-29 18:13:59 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-03-29 18:13:59 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2018-07-11 14:02:21 -07:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2015-04-02 21:47:49 -04:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2013-01-29 16:09:41 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-31 15:49:39 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2010-08-24 18:13:59 +00:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:21 -07:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2020-09-23 22:11:43 +08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2010-08-24 18:13:59 +00:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-24 18:13:59 +00:00
|
|
|
|
2022-06-12 13:42:32 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-22 19:47:50 +05:30
|
|
|
|
2022-12-18 18:03:54 +00:00
|
|
|
|
2010-06-22 19:47:50 +05:30
|
|
|
|
2022-12-18 18:03:54 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2020-09-23 22:11:43 +08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-29 16:09:41 -08:00
|
|
|
|
2022-12-18 18:03:54 +00:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
2020-09-23 22:11:43 +08:00
|
|
|
|
2022-12-18 17:57:27 +00:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-17 18:27:46 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-12 04:01:17 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2022-12-18 18:03:54 +00:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2020-09-23 22:11:43 +08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-12 04:01:17 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
2013-01-29 16:09:41 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-09 15:59:31 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-12 04:01:17 -05:00
|
|
|
|
2010-06-03 15:16:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-03 15:16:59 -07:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-03 15:16:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-03 15:16:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-22 10:13:12 -07:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
|
|
|
|
|
2010-10-22 10:13:12 -07:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-09-22 17:19:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
|
|
|
|
|
2011-07-11 16:40:58 +00:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
2022-06-12 13:42:32 +09:00
|
|
|
|
2012-02-26 14:49:57 -06:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-28 15:41:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-06-28 15:41:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2011-06-28 15:41:18 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2011-06-28 15:41:18 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:17 -05:00
|
|
|
|
2015-04-01 23:42:28 -04:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2015-04-01 23:42:28 -04:00
|
|
|
|
2015-08-15 15:49:13 +02:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2015-04-01 23:42:28 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2018-07-24 12:29:10 -07:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
2015-04-01 23:42:28 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
2011-01-28 17:05:59 -08:00
|
|
|
|
2015-04-01 23:42:28 -04:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
|
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
|
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
2024-01-09 12:39:03 +09:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2020-02-05 23:40:53 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-13 20:36:17 -05:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2015-08-15 15:49:13 +02:00
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-09 12:39:03 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2015-07-04 16:11:05 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-04 16:17:39 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2024-01-09 12:39:03 +09:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2022-06-10 11:42:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
2015-04-01 20:17:51 -04:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-18 20:29:53 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2008-10-13 18:45:24 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2009-07-14 13:25:41 -05:00
|
|
|
|
2008-10-17 16:20:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2009-04-05 16:26:41 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2009-04-05 16:26:41 -05:00
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
qid.type[1]
the type of the file (directory, etc.), represented as a bit
vector corresponding to the high 8 bits of the file's mode
word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
This patch implements the client side of getattr implementation for
9P2000.L. It introduces a new structure p9_stat_dotl for getting
Linux stat information along with QID. The data layout is similar to
stat structure in Linux user space with the following major
differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense
on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use
32 bit variables for these variables. However, some of the architectures
have used 64 bit variables and glibc exposes 64 bit variables to user
space on some architectures. Hence to be on the safer side we have made
these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 20:07:23 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
2009-04-05 16:22:16 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-15 19:01:56 -06:00
|
|
|
|
2009-04-05 16:22:16 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2009-04-05 16:22:16 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-05 16:22:16 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2009-04-05 16:22:16 -05:00
|
|
|
|
2010-03-05 18:50:14 +00:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2008-10-16 08:30:07 -05:00
|
|
|
|
2007-07-10 17:57:28 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
9p: Implement client side of setattr for 9P2000.L protocol.
SYNOPSIS
size[4] Tsetattr tag[2] attr[n]
size[4] Rsetattr tag[2]
DESCRIPTION
The setattr command changes some of the file status information.
attr resembles the iattr structure used in Linux kernel. It
specifies which status parameter is to be changed and to what
value. It is laid out as follows:
valid[4]
specifies which status information is to be changed. Possible
values are:
ATTR_MODE (1 << 0)
ATTR_UID (1 << 1)
ATTR_GID (1 << 2)
ATTR_SIZE (1 << 3)
ATTR_ATIME (1 << 4)
ATTR_MTIME (1 << 5)
ATTR_ATIME_SET (1 << 7)
ATTR_MTIME_SET (1 << 8)
The last two bits represent whether the time information
is being sent by the client's user space. In the absense
of these bits the server always uses server's time.
mode[4]
File permission bits
uid[4]
Owner id of file
gid[4]
Group id of the file
size[8]
File size
atime_sec[8]
Time of last file access, seconds
atime_nsec[8]
Time of last file access, nanoseconds
mtime_sec[8]
Time of last file modification, seconds
mtime_nsec[8]
Time of last file modification, nanoseconds
Explanation of the patches:
--------------------------
*) The kernel just copies relevent contents of iattr structure to
p9_iattr_dotl structure and passes it down to the client. The
only check it has is calling inode_change_ok()
*) The p9_iattr_dotl structure does not have ctime and ia_file
parameters because I don't think these are needed in our case.
The client user space can request updating just ctime by calling
chown(fd, -1, -1). This is handled on server side without a need
for putting ctime on the wire.
*) The server currently supports changing mode, time, ownership and
size of the file.
*) 9P RFC says "Either all the changes in wstat request happen, or
none of them does: if the request succeeds, all changes were made;
if it fails, none were."
I have not done anything to implement this specifically because I
don't see a reason.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-06-18 11:50:10 +05:30
|
|
|
|
|
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
9p: Implement client side of setattr for 9P2000.L protocol.
SYNOPSIS
size[4] Tsetattr tag[2] attr[n]
size[4] Rsetattr tag[2]
DESCRIPTION
The setattr command changes some of the file status information.
attr resembles the iattr structure used in Linux kernel. It
specifies which status parameter is to be changed and to what
value. It is laid out as follows:
valid[4]
specifies which status information is to be changed. Possible
values are:
ATTR_MODE (1 << 0)
ATTR_UID (1 << 1)
ATTR_GID (1 << 2)
ATTR_SIZE (1 << 3)
ATTR_ATIME (1 << 4)
ATTR_MTIME (1 << 5)
ATTR_ATIME_SET (1 << 7)
ATTR_MTIME_SET (1 << 8)
The last two bits represent whether the time information
is being sent by the client's user space. In the absense
of these bits the server always uses server's time.
mode[4]
File permission bits
uid[4]
Owner id of file
gid[4]
Group id of the file
size[8]
File size
atime_sec[8]
Time of last file access, seconds
atime_nsec[8]
Time of last file access, nanoseconds
mtime_sec[8]
Time of last file modification, seconds
mtime_nsec[8]
Time of last file modification, nanoseconds
Explanation of the patches:
--------------------------
*) The kernel just copies relevent contents of iattr structure to
p9_iattr_dotl structure and passes it down to the client. The
only check it has is calling inode_change_ok()
*) The p9_iattr_dotl structure does not have ctime and ia_file
parameters because I don't think these are needed in our case.
The client user space can request updating just ctime by calling
chown(fd, -1, -1). This is handled on server side without a need
for putting ctime on the wire.
*) The server currently supports changing mode, time, ownership and
size of the file.
*) 9P RFC says "Either all the changes in wstat request happen, or
none of them does: if the request succeeds, all changes were made;
if it fails, none were."
I have not done anything to implement this specifically because I
don't see a reason.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-06-18 11:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: Implement client side of setattr for 9P2000.L protocol.
SYNOPSIS
size[4] Tsetattr tag[2] attr[n]
size[4] Rsetattr tag[2]
DESCRIPTION
The setattr command changes some of the file status information.
attr resembles the iattr structure used in Linux kernel. It
specifies which status parameter is to be changed and to what
value. It is laid out as follows:
valid[4]
specifies which status information is to be changed. Possible
values are:
ATTR_MODE (1 << 0)
ATTR_UID (1 << 1)
ATTR_GID (1 << 2)
ATTR_SIZE (1 << 3)
ATTR_ATIME (1 << 4)
ATTR_MTIME (1 << 5)
ATTR_ATIME_SET (1 << 7)
ATTR_MTIME_SET (1 << 8)
The last two bits represent whether the time information
is being sent by the client's user space. In the absense
of these bits the server always uses server's time.
mode[4]
File permission bits
uid[4]
Owner id of file
gid[4]
Group id of the file
size[8]
File size
atime_sec[8]
Time of last file access, seconds
atime_nsec[8]
Time of last file access, nanoseconds
mtime_sec[8]
Time of last file modification, seconds
mtime_nsec[8]
Time of last file modification, nanoseconds
Explanation of the patches:
--------------------------
*) The kernel just copies relevent contents of iattr structure to
p9_iattr_dotl structure and passes it down to the client. The
only check it has is calling inode_change_ok()
*) The p9_iattr_dotl structure does not have ctime and ia_file
parameters because I don't think these are needed in our case.
The client user space can request updating just ctime by calling
chown(fd, -1, -1). This is handled on server side without a need
for putting ctime on the wire.
*) The server currently supports changing mode, time, ownership and
size of the file.
*) 9P RFC says "Either all the changes in wstat request happen, or
none of them does: if the request succeeds, all changes were made;
if it fails, none were."
I have not done anything to implement this specifically because I
don't see a reason.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-06-18 11:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
9p: Implement client side of setattr for 9P2000.L protocol.
SYNOPSIS
size[4] Tsetattr tag[2] attr[n]
size[4] Rsetattr tag[2]
DESCRIPTION
The setattr command changes some of the file status information.
attr resembles the iattr structure used in Linux kernel. It
specifies which status parameter is to be changed and to what
value. It is laid out as follows:
valid[4]
specifies which status information is to be changed. Possible
values are:
ATTR_MODE (1 << 0)
ATTR_UID (1 << 1)
ATTR_GID (1 << 2)
ATTR_SIZE (1 << 3)
ATTR_ATIME (1 << 4)
ATTR_MTIME (1 << 5)
ATTR_ATIME_SET (1 << 7)
ATTR_MTIME_SET (1 << 8)
The last two bits represent whether the time information
is being sent by the client's user space. In the absense
of these bits the server always uses server's time.
mode[4]
File permission bits
uid[4]
Owner id of file
gid[4]
Group id of the file
size[8]
File size
atime_sec[8]
Time of last file access, seconds
atime_nsec[8]
Time of last file access, nanoseconds
mtime_sec[8]
Time of last file modification, seconds
mtime_nsec[8]
Time of last file modification, nanoseconds
Explanation of the patches:
--------------------------
*) The kernel just copies relevent contents of iattr structure to
p9_iattr_dotl structure and passes it down to the client. The
only check it has is calling inode_change_ok()
*) The p9_iattr_dotl structure does not have ctime and ia_file
parameters because I don't think these are needed in our case.
The client user space can request updating just ctime by calling
chown(fd, -1, -1). This is handled on server side without a need
for putting ctime on the wire.
*) The server currently supports changing mode, time, ownership and
size of the file.
*) 9P RFC says "Either all the changes in wstat request happen, or
none of them does: if the request succeeds, all changes were made;
if it fails, none were."
I have not done anything to implement this specifically because I
don't see a reason.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-06-18 11:50:10 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-03-25 12:45:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
|
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-03-25 12:47:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2011-06-28 15:41:16 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:21 -07:00
|
|
|
|
|
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2023-10-25 19:34:44 +09:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2022-06-12 13:42:32 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:45 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
2023-05-03 16:49:29 +09:00
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-05-31 13:22:50 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-15 20:25:47 -04:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
|
|
|
|
|
2015-04-01 19:57:53 -04:00
|
|
|
|
|
|
|
|
|
2011-02-16 18:43:20 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2011-02-16 18:43:20 -08:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2011-02-16 18:43:20 -08:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
2017-04-14 17:22:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
2011-08-16 10:50:10 +05:30
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-04 13:41:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
2017-01-12 04:01:17 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-29 16:09:41 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-16 14:27:01 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
2017-01-12 04:01:17 -05:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2013-01-29 16:09:41 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
|
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-06-16 14:27:22 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 11:34:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
|
|
|
|
|
2021-11-02 22:16:43 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-09-27 12:22:13 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
2018-07-30 05:55:19 +00:00
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
|
|
|
|
|
2011-11-28 10:40:46 -08:00
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
2022-07-12 15:09:35 +09:00
|
|
|
|
2010-09-28 19:59:25 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-14 19:43:42 +02:00
|
|
|
|
2018-07-11 14:02:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|