{"push_id":3914300601,"size":6,"distinct_size":6,"ref":"refs/heads/fhs_media","head":"afcc516586ce3d8d8ca4af95b9836c2f057aa5dd","before":"27a1f28f814a2f59a1ff21857a613758be93952d","commits":[{"sha":"e16fdd2b76e862917e0407480247b268d508b377","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"udiskslinuxfilesystem: Don't compile systemd-specific code on non-systemd systems\n\nAlthough the HAVE_LIBSYSTEMD_LOGIN define is bound to libsystemd-login,\nit does check for libsystemd too and can be used to detect systemd presence.\nIt's used that way at other places after all.","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/e16fdd2b76e862917e0407480247b268d508b377"},{"sha":"4c7988eab6fc7a380a3b0435652740c9c6242f4f","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"udisksstate: Ignore state file read errors\n\nSince the state for the particular domain (the \"key\" argument) is\na single GVariant of type array, any modification is done via\ncopy-on-write -ish approach. Previously any state file read errors\n(except the file-not-found case) were treated as critical and\nno new state was stored. In such case the corrupted state file never\ngot chance to get overwritten by valid data. No state got stored\nin memory either, essentially making the whole UDisksState ineffective.\n\nThis commit ignores all state file read errors and continues with\nan empty state. This allows to continue working properly and fill both\nthe memory cache and the state file on the disk. Even in case\nof subsequent state file write errors the memory cache will assure\nUDisksState doing its job at least until the process ends\n(i.e. in a non-persistent way).\n\nAll errors are still being logged and printed on console.","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/4c7988eab6fc7a380a3b0435652740c9c6242f4f"},{"sha":"0efd8499e48189a3353f75b5cc8bbb2b772a6764","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"udiskslinuxfilesystem: Fix a typo","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/0efd8499e48189a3353f75b5cc8bbb2b772a6764"},{"sha":"6f216aca10ef33629a68f9b8e181ce69e6cd62ac","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"udisksstate: Distinguish between persistent and non-persistent mount points\n\nStoring persistent mount point state in a state file stored on\na non-persistent filesystem leads to state loss across system reboots.\nPreviously a systemd unit creation has been put in place to work around\nthis issue.\n\nThis change brings awareness of the mount persistency to UDisksState.\nThis is done by using separate state files for persistent and non-persistent\nmount points. The non-persistent state file would usually perish at the same\nmoment as the mount points (e.g. /run tmpfs mount). The persistent mount\npoints are stored in a state file stored on a persistent filesystem,\ntypically /var/lib.\n\nThe mount point state is being checked and cleaned up every time\na \"mount-removed\" signal is received from the mount monitor and also\non daemon startup. This has the nice positive effect of cleaning up\ndynamically created mount points on a persistent filesystem after reboot\nor when unmounted externally.","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/6f216aca10ef33629a68f9b8e181ce69e6cd62ac"},{"sha":"abdf281f57403aa15e0304478a31b2efe09700d8","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"udisksstate: Prefix some warnings and error messages\n\nSometimes it's difficult to identify context of the message.","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/abdf281f57403aa15e0304478a31b2efe09700d8"},{"sha":"afcc516586ce3d8d8ca4af95b9836c2f057aa5dd","author":{"name":"Tomas Bzatek","email":"d3a1cc6aceb7629c6bc23f72976a8a12cdfc8825@redhat.com"},"message":"Remove the systemd mount cleanup service\n\nNow that the mount point state has been split into persistent and non-persistent\ndatabase, mount points dynamically created by udisks are properly cleaned up across\nudisks daemon lifecycle, e.g. across system reboots. The only difference is that\nunused mount points are cleaned up the next time udisksd starts, contrary\nto cleaning when unmounted (right before system reboot).\n\nHowever the systemd cleanup service used to have several long-standing flaws:\n - ran async, creating race conditions like the mount point being removed twice:\n   first time by udisks itself on regular unmount and for the second time\n   undefined time after the unmount method call returned - conflicting with\n   scripts that reused the mount point for private affairs\n - security: no check whether the mount point was originally created by udisks\n   or by a foreign script (related to the race described above)\n - the cleanup service sometimes held the mount point busy for unknown reason\n - mount point cleaning didn't work at all on non-systemd systems","distinct":true,"url":"https://api.github.com/repos/tbzatek/udisks/commits/afcc516586ce3d8d8ca4af95b9836c2f057aa5dd"}]}
{"actor":{"display_login":"tbzatek"}}