Change in ...nfs-ganesha[next]: Clarify file handle swizzling methods
by Frank Filz (GerritHub)
Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507716 )
Change subject: Clarify file handle swizzling methods
......................................................................
Clarify file handle swizzling methods
Change-Id: I8b4cfda7543f4549196cfb4670e159f52a001df6
Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com>
---
M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_up.c
M src/include/fsal_api.h
2 files changed, 57 insertions(+), 27 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/16/507716/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507716
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I8b4cfda7543f4549196cfb4670e159f52a001df6
Gerrit-Change-Number: 507716
Gerrit-PatchSet: 1
Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com>
Gerrit-MessageType: newchange
3 years, 4 months
Change in ...nfs-ganesha[next]: Fix GTest build
by Daniel Gryniewicz (GerritHub)
Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507585 )
Change subject: Fix GTest build
......................................................................
Fix GTest build
Change-Id: Ia21a810f077fd84b092eeebe0c15fe4e772eabe3
Signed-off-by: Daniel Gryniewicz <dang(a)redhat.com>
---
M src/MainNFSD/libganesha_nfsd.ver
M src/gtest/fsal_api/test_readdir_correctness.cc
M src/gtest/fsal_api/test_readdir_latency.cc
M src/gtest/test_ci_hash_dist1.cc
M src/include/nfs_proto_functions.h
5 files changed, 6 insertions(+), 12 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/85/507585/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507585
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: Ia21a810f077fd84b092eeebe0c15fe4e772eabe3
Gerrit-Change-Number: 507585
Gerrit-PatchSet: 1
Gerrit-Owner: Daniel Gryniewicz <dang(a)redhat.com>
Gerrit-MessageType: newchange
3 years, 4 months
Change in ...nfs-ganesha[next]: Readdir - Don't back up dirent for whence-is-name
by Daniel Gryniewicz (GerritHub)
Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507584 )
Change subject: Readdir - Don't back up dirent for whence-is-name
......................................................................
Readdir - Don't back up dirent for whence-is-name
Early on in whence-is-name, we started caching the last 2 dirents to
make it easier to continue a readdir. However, we later switched to
caching them all, on an LRU. This chunk of code was added in the first
set, but not removed in the second. This will result in a double-unref
of an entry when the chunk is released, since we're starting with an
entry that was already unref'd.
Change-Id: I14995bb9432b60e5d5c35ab4faaa344247529352
Signed-off-by: Daniel Gryniewicz <dang(a)redhat.com>
---
M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_helpers.c
1 file changed, 0 insertions(+), 11 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/84/507584/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507584
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I14995bb9432b60e5d5c35ab4faaa344247529352
Gerrit-Change-Number: 507584
Gerrit-PatchSet: 1
Gerrit-Owner: Daniel Gryniewicz <dang(a)redhat.com>
Gerrit-MessageType: newchange
3 years, 4 months
Change in ...nfs-ganesha[next]: FSAL_CEPH: make consistency for create_handle
by freeze (GerritHub)
freeze has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507499 )
Change subject: FSAL_CEPH: make consistency for create_handle
......................................................................
FSAL_CEPH: make consistency for create_handle
In commit 101cfb8, create_handle would check the handle buffer
with struct ceph_handle_key instead ceph_host_handle.
ceph_handle_key contains export_id and ceph_host_handle.
The export id would be used in FSAL_CEPH (putfh in nfs4/
FhandleToCache in nfs3).
We should make the handle buffer consistency with ceph_handle_key
to avoid EINVAL with create_handle.
So make handle_to_wire consider the later struct ceph_handle_key,
that also make create_handle would check the same struct.
That would fix the regression with 101cfb8 with nfs3 readdir case.
Change-Id: I4a55ff6a470fb0922b82b6f24a1ba20def4b7e95
Signed-off-by: Vicente Cheng <freeze.bilsted(a)gmail.com>
---
M src/FSAL/FSAL_CEPH/handle.c
1 file changed, 10 insertions(+), 7 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/99/507499/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507499
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I4a55ff6a470fb0922b82b6f24a1ba20def4b7e95
Gerrit-Change-Number: 507499
Gerrit-PatchSet: 1
Gerrit-Owner: freeze <freeze.bilsted(a)gmail.com>
Gerrit-MessageType: newchange
3 years, 4 months
Change in ...nfs-ganesha[next]: config: restrict default protocols to nfs3/4
by Dominique Martinet (GerritHub)
Dominique Martinet has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507433 )
Change subject: config: restrict default protocols to nfs3/4
......................................................................
config: restrict default protocols to nfs3/4
The documentation already states that default protocols are
nfs3 and nfs4, but everything was enabled incorrectly.
Make defaults more restrictive as documented
Change-Id: I2b3e3d813d400423f0de3b2a5d7454aed657a7c5
Signed-off-by: Dominique Martinet <dominique.martinet(a)cea.fr>
---
M src/support/nfs_read_conf.c
1 file changed, 4 insertions(+), 7 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/33/507433/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507433
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I2b3e3d813d400423f0de3b2a5d7454aed657a7c5
Gerrit-Change-Number: 507433
Gerrit-PatchSet: 1
Gerrit-Owner: Dominique Martinet <asmadeus(a)codewreck.org>
Gerrit-MessageType: newchange
3 years, 4 months
Announce Push of V4-dev.45
by Frank Filz
Branch next
Tag:V4-dev.45
Merge Highlights
* FSAL_RGW: allow readdir() to continue past damaged objects
Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com>
Contents:
da6685b Frank S. Filz V4-dev.45
c651e4e Matt Benjamin FSAL_RGW: allow readdir() to continue past damaged
objects
3 years, 4 months
Change in ...nfs-ganesha[next]: FSAL_RGW: allow readdir() to continue past damaged objects
by Matt Benjamin (GerritHub)
Matt Benjamin has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507249 )
Change subject: FSAL_RGW: allow readdir() to continue past damaged objects
......................................................................
FSAL_RGW: allow readdir() to continue past damaged objects
The current FSAL_RGW readdir loop performs a lookup on each
object returned from enumeration, as expected, but stops
enumeration if any lookup fails.
In order to avoid truncated listings in the presence of (e.g.)
a damaged bucket or leaf object, log a warning in the failed
lookup case, but do not terminate the readdir.
Change-Id: Iaf07b6853a3d81ba150d241089f45605ec88920a
Signed-off-by: Matt Benjamin <mbenjamin(a)redhat.com>
---
M src/FSAL/FSAL_RGW/handle.c
1 file changed, 9 insertions(+), 2 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/49/507249/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/507249
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: Iaf07b6853a3d81ba150d241089f45605ec88920a
Gerrit-Change-Number: 507249
Gerrit-PatchSet: 1
Gerrit-Owner: Matt Benjamin <mbenjamin(a)redhat.com>
Gerrit-MessageType: newchange
3 years, 4 months
[FOSDEM] CfP Software Defined Storage devroom
by Niels de Vos
FOSDEM is a free software event that offers open source communities a place to
meet, share ideas and collaborate. It is well known for being highly
developer-oriented and in the past brought together 8000+ participants from all
over the world. It's home is in the city of Brussels (Belgium).
FOSDEM 2021 will take place as an online event during the weekend of February
6./7. 2021. More details about the event can be found at http://fosdem.org/
** Call For Participation
The Software Defined Storage devroom will go into it's fifth round for talks
around Open Source Software Defined Storage projects, management tools
and real world deployments.
Presentation topics could include but are not limited too:
- Your work on a SDS project like Ceph, Gluster, OpenEBS, CORTX or Longhorn
- Your work on or with SDS related projects like OpenStack SWIFT or Container
Storage Interface
- Management tools for SDS deployments
- Monitoring tools for SDS clusters
** Important dates:
- Dec 27th 2020: submission deadline for talk proposals
- Dec 31st 2020: announcement of the final schedule
- Feb 6th 2021: Software Defined Storage dev room
Talk proposals will be reviewed by a steering committee:
- Niels de Vos (OpenShift Container Storage Developer - Red Hat)
- Jan Fajerski (Ceph Developer - SUSE)
- TBD
Use the FOSDEM 'pentabarf' tool to submit your proposal:
https://penta.fosdem.org/submission/FOSDEM21
- If necessary, create a Pentabarf account and activate it.
Please reuse your account from previous years if you have
already created it.
https://penta.fosdem.org/user/new_account/FOSDEM21
- In the "Person" section, provide First name, Last name
(in the "General" tab), Email (in the "Contact" tab)
and Bio ("Abstract" field in the "Description" tab).
- Submit a proposal by clicking on "Create event".
- If you plan to register your proposal in several tracks to increase your chances,
don't! Register your talk once, in the most accurate track.
- Presentations have to be pre-recorded before the event and will be streamed on
the event weekend.
- Important! Select the "Software Defined Storage devroom" track
(on the "General" tab).
- Provide the title of your talk ("Event title" in the "General" tab).
- Provide a description of the subject of the talk and the
intended audience (in the "Abstract" field of the "Description" tab)
- Provide a rough outline of the talk or goals of the session (a short
list of bullet points covering topics that will be discussed) in the
"Full description" field in the "Description" tab
- Provide an expected length of your talk in the "Duration" field.
We suggest a length between 15 and 45 minutes.
** For accepted talks
Once your proposal is accepted we will assign you a volunteer deputy who will
help you to produce the talk recording. The volunteer will also try to ensure
the recording is of good quality, help with uploading it to the system,
broadcasting it during the event and moderate the Q&A session after the
broadcast. Please note that as a presenter you're expected to be available
online during and especially after the broadcast of you talk. The schedule will
be available under
https://fosdem.org/2021/schedule/track/software_defined_storage/
Hope to hear from you soon! And please forward this announcement.
If you have any further questions, please write to the mailing list at
storage-devroom(a)lists.fosdem.org and we will try to answer as soon as
possible.
Thanks!
_______________________________________________
FOSDEM mailing list
FOSDEM(a)lists.fosdem.org
https://lists.fosdem.org/listinfo/fosdem
3 years, 4 months
Announce Push of V4-dev.44
by Frank Filz
Branch next
Tag:V4-dev.44
Merge Highlights
* mdcache_lru.c: assert refcount consistency
* atomic_x86_64.h: use compiler instrinsics instead
Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com>
Contents:
f3cb6b9 Frank S. Filz V4-dev.44
75bceae Matthew DeVore atomic_x86_64.h: use compiler instrinsics instead
124a0d2 Matthew DeVore mdcache_lru.c: assert refcount consistency
3 years, 4 months
