Bug 1047404 - Occasional polkitd segs (at ....71c8)
Summary: Occasional polkitd segs (at ....71c8)
Keywords:
Status: CLOSED DUPLICATE of bug 910262
Alias: None
Product: Fedora
Classification: Fedora
Component: polkit
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-31 00:31 UTC by Dr. David Alan Gilbert
Modified: 2014-01-02 13:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-02 13:49:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dr. David Alan Gilbert 2013-12-31 00:31:36 UTC
Description of problem:
Looking in a dmesg I noticed polkitd had seg'd
Dec 31 00:10:01 major kernel: polkitd[796]: segfault at 7f77281071c8 ip 00007f77281071c8 sp 00007fffb1720bc8 error 15


Version-Release number of selected component (if applicable):
polkit-0.112-2.fc20.x86_64


How reproducible:
Happen 5 times in the last couple of months, no apparent pattern

Steps to Reproduce:
1. I'm only noticing this from the logs, so not got steps
2.
3.

Actual results:
[dg@major ~]$ journalctl |grep -i polkit|grep -i seg
Nov 10 21:01:02 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Nov 19 16:00:01 major kernel: polkitd[745]: segfault at 7f3e461071c8 ip 00007f3e461071c8 sp 00007fff9b17e5d8 error 15
Nov 19 16:00:01 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Nov 24 01:01:01 major kernel: polkitd[741]: segfault at 7fcf12d071c8 ip 00007fcf12d071c8 sp 00007fff53f8eb88 error 15
Nov 24 01:01:01 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Nov 26 16:50:01 major kernel: polkitd[737]: segfault at 7fd7244071c8 ip 00007fd7244071c8 sp 00007fff26ced8e8 error 15
Nov 26 16:50:01 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Dec 08 01:55:48 major kernel: polkitd[804]: segfault at 7fd56a0071c8 ip 00007fd56a0071c8 sp 00007ffff2c77938 error 15
Dec 08 01:55:48 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Dec 31 00:10:01 major kernel: polkitd[796]: segfault at 7f77281071c8 ip 00007f77281071c8 sp 00007fffb1720bc8 error 15
Dec 31 00:10:01 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV


Expected results:
No segs

Additional info:

Note they all seem to be ..071c8 addresses, so it seems to be the same address, which also I think is the IP which seems pretty weird/worrying.
I don't think I was doing anything odd at the time.
I have one extra added polkit rule:
[root@major dg]# cat /etc/polkit-1/rules.d/10.virt.rules 
polkit.addRule(function(action, subject) {
        polkit.log("action=" + action);
        polkit.log("subject=" + subject);
        var now = new Date();
        polkit.log("now=" + now)
        if ((action.id == "org.libvirt.unix.manage" || action.id == "org.libvirt.unix.monitor") && subject.isInGroup("virt")) {
        return polkit.Result.YES;
        }
        return null;
        });

but I've not been doing anything with virt on this machine today, probably was on previous days.

Journalctl doesn't say much more:
Dec 31 00:10:01 major polkitd[796]: /etc/polkit-1/rules.d/10.virt.rules:2: action=[Action id='org.freedesktop.NetworkManager.wifi.share.protected']
Dec 31 00:10:01 major polkitd[796]: /etc/polkit-1/rules.d/10.virt.rules:3: subject=[Subject pid=1688 user='dg' groups=dg,wheel,dialout,virt, seat='seat0' session='1' local=true active=true]
Dec 31 00:10:01 major polkitd[796]: /etc/polkit-1/rules.d/10.virt.rules:5: now=Tue Dec 31 2013 00:10:01 GMT+0000 (GMT)
Dec 31 00:10:01 major kernel: polkitd[796]: segfault at 7f77281071c8 ip 00007f77281071c8 sp 00007fffb1720bc8 error 15
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message 
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bu
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.network-control: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.sleep-wake: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-network: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bu
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major NetworkManager[858]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 31 00:10:01 major systemd[1]: polkit.service: main process exited, code=killed, status=11/SEGV
Dec 31 00:10:01 major systemd[1]: Unit polkit.service entered failed state.

Comment 1 Miloslav Trmač 2014-01-02 13:49:47 UTC
Thanks for your report.  This is very likely a duplicate of #910262; next steps to diagnosing this would be getting a full core dump (which is somewhat difficult because the kernel's policy prohibits this for a process which behaves like polkitd).

*** This bug has been marked as a duplicate of bug 910262 ***


Note You need to log in before you can comment on or make changes to this bug.