| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes CID#1502330.
|
| |
|
|
|
|
|
| |
Let's break a huge function in two. No code change, just some
refactoring.
|
| |
|
|
|
|
|
| |
We use this pattern all the time in order to thward extension attacks,
add a helper to make it shorter.
|
|
|
|
|
|
| |
Let's not regress in entropy in any case.
This does what f913c784ad4c93894fd6cb2590738113dff5a694 also does.
|
|
|
|
|
|
| |
Let's do a careful, focussed sync at the right places instead of a
blanket sync at the end. After all we want to run this on every boot
soon.
|
|
|
|
|
|
|
|
| |
This doesn't really fix anything, but in general we should put stronger
emphasis on operating via dir fds rather than paths more (in particular
when writing files as opposed to consuming them).
No real change in behaviour.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-1 was used everywhere, but -EBADF or -EBADFD started being used in various
places. Let's make things consistent in the new style.
Note that there are two candidates:
EBADF 9 Bad file descriptor
EBADFD 77 File descriptor in bad state
Since we're initializating the fd, we're just assigning a value that means
"no fd yet", so it's just a bad file descriptor, and the first errno fits
better. If instead we had a valid file descriptor that became invalid because
of some operation or state change, the other errno would fit better.
In some places, initialization is dropped if unnecessary.
|
|
|