Bug 2178799
| Summary: | Feature request: support for NFS with TLS | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Olga Kornieskaia <kolga> |
| Component: | kernel | Assignee: | Jeff Layton <jlayton> |
| kernel sub component: | NFS | QA Contact: | JianHong Yin <jiyin> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | bcodding, jlayton, ondrej.valousek, plambri, rahsingh, tbecker, xzhou, yieli, yoyang |
| Version: | 9.4 | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-23 11:35:10 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Olga Kornieskaia
2023-03-15 18:29:05 UTC
There has been a lot of progress on this upstream. There are now a working prototype NFS client and server patches that use a netlink-based mechanism to hand off TLS negotiation to userland. Hannes Reinecke also has some prototype patches for nvme over tls that use the same upcall. There are still some details to be worked out, but this seems like the way forward so far. We're (tentatively) hoping that some of these patches will make their way into v6.4 upstream, but it's still too early to know. Relevant patch postings so far: https://lore.kernel.org/kernel-tls-handshake/167726551328.5428.13732817493891677975.stgit@91.116.238.104.host.secureserver.net/T/#t https://lore.kernel.org/kernel-tls-handshake/167932094748.3131.11264549266195745851.stgit@manet.1015granger.net/T/#t https://lore.kernel.org/kernel-tls-handshake/c90f39ed-1bcc-7a8f-fd2d-ee4663e94bb4@suse.de/T/#t There are also NFS client patches, but they haven't been reposted lately. At this point, I'm going to go ahead set the ITR for RHEL9.4. Hopefully by later this summer we should be ready to backport something for this. (In reply to Jeff Layton from comment #2) ... > At this point, I'm going to go ahead set the ITR for RHEL9.4. Please note that we'll start to use Jira (instead of Bugzilla) to process the RHEL update. Thus this is a candidate to be migrated to Jira. *** Bug 2230453 has been marked as a duplicate of this bug. *** I've started an initial backport of this, based on Chris Leech's backport of the nvmeof work. The current plan is to target 9.4. Draft backport is here. It'll probably need several iterations before it's ready for inclusion:
https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2909
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. *** Bug 2136452 has been marked as a duplicate of this bug. *** |