LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Friday, June 26th, 2020
| Time |
Event |
| 1:14p |
Security updates for Friday
Security updates have been issued by Debian (alpine), Fedora (fwupd, microcode_ctl, mingw-libjpeg-turbo, mingw-sane-backends, suricata, and thunderbird), openSUSE (uftpd), Red Hat (nghttp2), SUSE (ceph, curl, mutt, squid, tigervnc, and unbound), and Ubuntu (linux kernel and nvidia-graphics-drivers-390, nvidia-graphics-drivers-440). | | 2:40p |
[$] Managing tasks with todo.txt and Taskwarrior One quote from Douglas Adams has always stayed with me: " I love
deadlines. I like the whooshing sound they make as they fly by". We
all lead busy lives and few ever see the bottom of our long to-do lists.
One of the oldest items on my list, ironically, is to find a better system
to manage all my tasks. Can task-management systems make us more productive
while, at the same time, reducing the stress caused by the sheer number of
outstanding tasks?
This article, from guest author Martin Michlmayr, looks at todo.txt and Taskwarrior. | | 3:10p |
Using syzkaller, part 4: Driver fuzzing Ricardo Cañuelo Navarro describes
the challenges associated with fuzzing complex device drivers with Syzkaller — and some solutions. " V4L2, however, is only supported in the sense that
the involved system calls (including the myriad V4L2 ioctls) and data
structures are described. This is already useful and, equipped with those
descriptions, Syzkaller has been able to find many V4L2 bugs. But the
fuzzing process contains a lot of randomness and, while that's a good thing
in many cases when it comes to fuzzing, due to the complexity of the V4L2
API, simply randomizing the system calls and its inputs may not be enough
to reach most of the code in some drivers, especially in drivers with
complicated interfaces such as those based on the Request API, including
stateless drivers." |
|