Bug 1635584

Summary:	Add man pages for open_by_handle_at(2) and name_by_handle_at(2)
Product:	Red Hat Enterprise Linux 7	Reporter:	Piyush Bhoot <pbhoot>
Component:	man-pages-overrides	Assignee:	Nikola Forró <nforro>
Status:	CLOSED ERRATA	QA Contact:	Jan Houska <jhouska>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	hhorak, jamills, jhouska, tdavis
Target Milestone:	rc	Keywords:	ManPageChange
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	man-pages-overrides-7.7.0-1.el7	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 12:33:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1653236, 1661173

Description Piyush Bhoot 2018-10-03 10:32:55 UTC

1. Description of problem:
[RFE] Add man pages for open_by_handle_at(2) and name_by_handle_at(2)

2. Who is the customer behind the request?
Customer: 	DeepSpace Storage System, Inc
Account Number: 	6115658
Strategic: No

3. What is the nature and description of the request?

open_by_handle_at(2) and name_by_handle_at(2) are defined system calls and accessible via glibc , Because it is defined in glibc I was assuming that suitable man pages would be available

4.  Why does the customer need this? (List the business requirements here)
 Developers rely on standard documentation. 

5. How would the customer like to achieve this? (List the functional requirements here)
man pages for open_by_handle_at(2) and name_by_handle_at(2)

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.

7. Does the customer have any specific timeline dependencies and which release would they like to target?

Not specified.

8. Is the sales team involved in this request and do they have any additional input?
No.

9. Would the customer be able to assist in testing this functionality if implemented?
Yes

Comment 8 Jan Houska 2019-06-25 09:51:52 UTC

NEW PASS:
man-pages-overrides-7.7.3-1.el7

#man open_by_handle_at
..

NAME
       name_to_handle_at, open_by_handle_at - obtain handle for a pathname and open file via a handle

SYNOPSIS
       #define _GNU_SOURCE         /* See feature_test_macros(7) */
       #include <sys/types.h>
       #include <sys/stat.h>
       #include <fcntl.h>

       int name_to_handle_at(int dirfd, const char *pathname,
                             struct file_handle *handle,
                             int *mount_id, int flags);

       int open_by_handle_at(int mount_fd, struct file_handle *handle,
                             int flags);

DESCRIPTION
       The  name_to_handle_at()  and open_by_handle_at() system calls split the functionality of openat(2) into two parts: name_to_handle_at() returns an opaque handle that corresponds
       to a specified file; open_by_handle_at() opens the file corresponding to a handle returned by a previous call to name_to_handle_at() and returns an open file descriptor.

   name_to_handle_at()
       The name_to_handle_at() system call returns a file handle and a mount ID corresponding to the file specified by the dirfd and pathname arguments.  The file  handle  is  returned
       via the argument handle, which is a pointer to a structure of the following form:
....
SEE ALSO
       open(2), libblkid(3), blkid(8), findfs(8), mount(8)

       The libblkid and libmount documentation in the latest util-linux release at ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩

Linux                                                                                  2017-09-15                                                                   OPEN_BY_HANDLE_AT(2)


OLD FAIL:
man-pages-overrides-7.6.2-1.el7

#man open_by_handle_at
No manual entry for open_by_handle_at

Comment 10 errata-xmlrpc 2019-08-06 12:33:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2034