[Rpm-maint] [rpm-software-management/rpm] fapolicyd: Make write() nonblocking (PR #2166)

[Radovan Sroka]

> What's missing from the commit message is the all-important _why_ part. Does this fix a bug (what happens etc) or what?

Sometimes during the system update/upgrade fapolicyd get restarted e.g. when systemd gets updated. That can lead to the situation where fapolicyd pipe has been removed and created again. In such cases rpm-plugin-fapolicyd gets stuck on write() to the pipe which does not exist anymore. After switching to non blocking file descriptor we can try to reopen the pipe if there is an error from write(). Assuming that a new pipe should appear when fapolicyd daemon starts again. If not then after 1 minute of waiting we expect fapolicyd daemon to be not active and we let the transaction continue.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2166#issuecomment-1232607461
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/2166/c1232607461 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220831/9a3ac9f6/attachment.html>