[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: close() behavior when there are multiple fds for a socket
|
From: |
Eric Blake |
|
Subject: |
Re: close() behavior when there are multiple fds for a socket |
|
Date: |
Fri, 15 Oct 2021 13:40:11 -0500 |
|
User-agent: |
NeoMutt/20210205-854-613e2c |
On Fri, Oct 15, 2021 at 09:10:04AM -0700, Ben Pfaff wrote:
> What a bureaucratic organization! The bug report form, once I got a login,
> requires one to specify a page number and line number, but it seems that
> you can only get the PDF version of the spec that has that information if
> you belong to an organization that is a member, so I filled those in with "?"
> and am hoping for the best.
That's fine. Adding page numbers after the fact is something that
happens rather frequently; and I've done in for your bug in particular
just now.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
- close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Paul Eggert, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Paul Eggert, 2021/10/14
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/15
- Re: close() behavior when there are multiple fds for a socket,
Eric Blake <=
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/15
- Re: close() behavior when there are multiple fds for a socket, Bernhard Voelker, 2021/10/21
- Re: close() behavior when there are multiple fds for a socket, Ben Pfaff, 2021/10/21