On 7 Feb 02 at 8:45, Patrick Mochel wrote:
> On Thu, 7 Feb 2002, Andrey Panin wrote:
> > Attached patch adds check that returned value is less then requested
> > byte count. I know that actual callback function device_read_status()
> > should also be fixed, but I found this bug after midnight and
> > decided to sleep a little :)
>
> That sanity check was in there, once upon a time. However, in moving the
> weight from the driver callbacks to the driverfs read_file() and
> write_file(), it must have got dropped...
>
> Thank you. It's been applied and will be pushed forward.
[I have only 2.5.3 sources here yet]
Can you also check for size >= PAGE_SIZE on enter to entry->show()
procedure? It looks ugly to me that each driver has to check for this
constant unless it wants to smash some innocent kernel memory.
And neither of driverfs_read_file nor driverfs_write_file supports
semantic we use with other filesystems: If at least one byte was
read/written, return byte count (even if error happens). Only if zero
bytes was written, return error code.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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/
This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:01:03 EST