user jobs cause kernel panic
Bug #807293 reported by
ValVe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
High
|
James Hunt |
Bug Description
Any job in ~/.init/ started as non-root causes error in initctl and then init crashes.
testjob.conf is in ~/.init/ (and runs just fine as root when placed in /etc/init/)
valve@webcast1:~$ initctl start testjob
initctl: Message did not receive a reply (timeout by message bus)
and then kernel panics ^_^
Changed in upstart: | |
status: | Confirmed → In Progress |
Changed in upstart: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This behavior occurs in both natty upstart package and 1.3 built from source. (DBus access rules taken from 1.3 in both cases)
$ cat $HOME/. init/testjob. conf
#### the test job ####
description "Crashes your system"
task
script
end script
#### end test job
$ initctl --system start testjob
initctl: Message did not receive a reply (timeout by message bus)
Init crashes only if the job executes any command or has "script - end script", even if it's empty.
Jobs starting on signals and with dbus-send like that also crash init. com.ubuntu. Upstart /com/ubuntu/ Upstart/ jobs/1000/ testjob com.ubuntu. Upstart0_ 6.Job.Stop array:string: boolean:true
$ dbus-send --system --print-reply --dest=
Abstract jobs which do nothing (do not contain exec or script statements) start and stop as they should. Starting on manually emitted signals also work with those jobs.