Re: lseek on /proc/kmsg

[Jan Engelhardt <jengelh@linux01.gwdg.de>]

1> Sure, read() needs to be modified to respect the file-position
1> set by kmsg_seek(). I don't think you can get away with the
1> call back into do_syslog.

2>I'm not sure that seek makes any sense on that, since it is more like a 
2>pipe than a normal file..

Well, seek(fd, 0, SEEK_END) could be used to flush a pipe's buffers.

0>> +static loff_t kmsg_seek(struct file *filp, loff_t offset, int origin) {
0>> +    if(origin != 2 /* SEEK_END */ || offset < 0) { return -ESPIPE; }
3> "Allow" seeking past the end of the buffer?

Well, what does lseek(fd, >0, SEEK_END) do on normal files?



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/