| 1 |
Joshua Brindle wrote: |
| 2 |
|
| 3 |
> IIRC we looked into this and it's a one liner but there was a |
| 4 |
> Changelog explaination that said they did it so the pipe would stay |
| 5 |
> open between messages ?! whatever that means. |
| 6 |
> however a quick look in linux/fs/proc/kmsg.c shows that kmsg doesn't |
| 7 |
> have a write handler anyway |
| 8 |
> |
| 9 |
> struct file_operations proc_kmsg_operations = { |
| 10 |
> .read = kmsg_read, |
| 11 |
> .poll = kmsg_poll, |
| 12 |
> .open = kmsg_open, |
| 13 |
> .release = kmsg_release, |
| 14 |
> }; |
| 15 |
> |
| 16 |
> So there is no harm in allowing this. |
| 17 |
|
| 18 |
Thank you very much! |
| 19 |
I'll update my policy accordingly. |
| 20 |
|
| 21 |
regards, |
| 22 |
nixnut |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-hardened@g.o mailing list |
Archives