read of /proc/uptime could fail and cause exit

Bug #1708461 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pollinate (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

As i noticed when reviewing changes for bug 1708192, I noticed that
the read of /proc/uptime could fail.

This is re-creatable with something like this:
$ mp=/tmp/my.d
$ mkdir -p $mp
$ sudo mount --bind / $mp

# need /dev/ mounted for 'logger' usage (/dev/log) which is also fatal
$ sudo mount --bind /dev $mp/dev

# need /run because in systemd systems, /dev/log is a link to
# /run/systemd/journal/dev-log
$ sudo mount --bind /run $mp/run
$ sudo chroot $mp pollinate --reseed
<13>Aug 3 14:06:32 pollinate[6449]: system was previously seeded at [2017-08-02 18:11:17.357060419 +0000]
<13>Aug 3 14:06:32 pollinate[6449]: client sent challenge to [https://entropy.ubuntu.com/]
grep: /proc/cpuinfo: No such file or directory
/usr/bin/pollinate: 102: /usr/bin/pollinate: cannot open /proc/uptime: No such file
$ echo $?
2

Scott Moser (smoser)
Changed in pollinate (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pollinate - 4.26-1

---------------
pollinate (4.26-1) artful; urgency=medium

  [ Scott Moser ]
  * Perform as safe read of /proc/uptime LP: #1708461

  [ Dimitri John Ledkov ]
  * Drop upstart system job
  * Drop no longer needed build-deps, and redundantly specified essential
    bsdutils
  * Fix spelling typo in the description
  * Bump debhelper compat to 9, previous levels are deprecated

 -- Dimitri John Ledkov <email address hidden> Fri, 18 Aug 2017 13:19:15 +0100

Changed in pollinate (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.