From: Cyrill Gorcunov <gorcunov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH man] kcmp: Add KCMP_EPOLL_TFD description
Date: Tue, 15 Aug 2017 22:57:43 +0300 [thread overview]
Message-ID: <20170815195743.GE14341@uranus> (raw)
In-Reply-To: <1529b66d-5caa-7f34-251f-ec23428c418e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, Aug 15, 2017 at 09:49:47PM +0200, Michael Kerrisk (man-pages) wrote:
> Hello Cyril,
>
>
> On 08/06/2017 09:38 AM, Cyrill Gorcunov wrote:
> > KCMP_EPOLL_TFD
> > Check whether the file descriptor idx1 of process pid1 present in epoll(7)
> > instance described by idx2 of process pid2. The argument idx2 is an
> > address of structure where the target file is described.
> >
> > struct kcmp_epoll_slot {
> > __u32 efd;
> > __u32 tfd;
> > __u64 toff;
> > };
> >
> > where efd is epoll file descriptor from epoll_create(2) call, tfd is a
> > target file number, toff is a target file offset counted from zero. Sev‐
> > eral different targets may be registered with the same file descriptor
> > number and setting specific offset helps to investigate each of them.
>
> Thanks. I've applied this patch. Is there some example program that
> demonstrates the use of this feature?
Well, not as its own. There are a series floating around for CRIU not merged
yet since I need to rebase it on new CRIU release and resend, but there is
a sample https://lists.openvz.org/pipermail/criu/2017-February/036041.html
- the file added into epoll, then dup'ed and original is closed, so kcmp
with dup'ed instance should match kcmp call.
If you can wait I'll try to find some time on the week and rather update
kernel selftests for this new kcmp mode and CC you on the patch. Sounds OK?
prev parent reply other threads:[~2017-08-15 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 7:38 [PATCH man] kcmp: Add KCMP_EPOLL_TFD description Cyrill Gorcunov
[not found] ` <20170806073858.GB1916-ZmlpmtaulQd+urZeOPWqwQ@public.gmane.org>
2017-08-15 19:49 ` Michael Kerrisk (man-pages)
[not found] ` <1529b66d-5caa-7f34-251f-ec23428c418e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-15 19:57 ` Cyrill Gorcunov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170815195743.GE14341@uranus \
--to=gorcunov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox