This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author izbyshev
Recipients gregory.p.smith, izbyshev, kevans, kevans91
Date 2022-04-08.15:25:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1649431558.86.0.443300350725.issue47260@roundup.psfhosted.org>
In-reply-to
Content
> It's been years now and that hasn't happened, even with more recent flag additions. I think it's safe to say it won't, and such a fallback upon error won't put us back into a bogus pre-close_range situation where we're needlessly close()ing a bunch of closed fds.

Yes, I also find it unlikely that close_range() will start reporting an error if it fails to close some fd, especially if not given some new flag. Such error reporting doesn't seem very useful to userspace because there is no way to associate the error with the fd.

But even if such change happens, it will be just a performance regression, not a potential correctness/security issue.
History
Date User Action Args
2022-04-08 15:25:58izbyshevsetrecipients: + izbyshev, gregory.p.smith, kevans, kevans91
2022-04-08 15:25:58izbyshevsetmessageid: <1649431558.86.0.443300350725.issue47260@roundup.psfhosted.org>
2022-04-08 15:25:58izbyshevlinkissue47260 messages
2022-04-08 15:25:58izbyshevcreate