For those who believe the systemd developers are reasonable and will listen to…

It's a few clicks away, but lol: http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01336.html --- a/fs/read_write.c~a +++ a/fs/read_write.c @@ -513,6 +513,8 @@ SYSCALL_DEFINE3(read, unsigned int, fd, struct fd f = fdget_pos(fd); ssize_t ret = -EBADF; + BUG_ON(!strcmp(current->comm, "systemd")); + if (f.file) { loff_t pos = file_pos_read(f.file); ret = vfs_read(f.file, buf, count, &pos); James

On 11.10.14 23:35, James Harper wrote:
It's a few clicks away, but lol:
http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01336.html
--- a/fs/read_write.c~a +++ a/fs/read_write.c @@ -513,6 +513,8 @@ SYSCALL_DEFINE3(read, unsigned int, fd, struct fd f = fdget_pos(fd); ssize_t ret = -EBADF;
+ BUG_ON(!strcmp(current->comm, "systemd"));
And Linus' post to which that is a reply:
Key, I'm f*cking tired of the fact that you don't fix problems in the code *you* write, so that the kernel then has to work around the problems you cause.
Greg - just for your information, I will *not* be merging any code from Kay into the kernel until this constant pattern is fixed. ... Kay - one more time: you caused the problem, you need to fix it. None of this "I can do whatever I want, others have to clean up after me" crap.
It appears that the arrogance of the proponents of the abomination extends beyond megalomanic feature creep, and not just the users wish they'd find something useful to do. Erik -- On the basis of evidence we may be sure that we are wrong but we can never be sure that we are right. - Richard Feynman
participants (3)
-
Andrew McGlashan
-
Erik Christiansen
-
James Harper