Searched hist:"24754 db2728a87c513cc480c70c09072a7a40ba6" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/fuse/ |
| H A D | fuse_i.h | diff 24754db2728a87c513cc480c70c09072a7a40ba6 Mon Apr 20 10:54:38 CDT 2020 Max Reitz <mreitz@redhat.com> fuse: store fuse_conn in fuse_req
Every fuse_req belongs to a fuse_conn. Right now, we always know which
fuse_conn that is based on the respective device, but we want to allow
multiple (sub)mounts per single connection, and then the corresponding
filesystem is not going to be so trivial to obtain.
Storing a pointer to the associated fuse_conn in every fuse_req will
allow us to trivially find any request's superblock (and thus
filesystem) even then.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
| H A D | dev.c | diff 24754db2728a87c513cc480c70c09072a7a40ba6 Mon Apr 20 10:54:38 CDT 2020 Max Reitz <mreitz@redhat.com> fuse: store fuse_conn in fuse_req
Every fuse_req belongs to a fuse_conn. Right now, we always know which
fuse_conn that is based on the respective device, but we want to allow
multiple (sub)mounts per single connection, and then the corresponding
filesystem is not going to be so trivial to obtain.
Storing a pointer to the associated fuse_conn in every fuse_req will
allow us to trivially find any request's superblock (and thus
filesystem) even then.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|