RE: SYSLOG_ACTION_READ_ALL question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: kernelnewbies-bounces@xxxxxxxxxxxxxxxxx [mailto:kernelnewbies-
> bounces@xxxxxxxxxxxxxxxxx] On Behalf Of william douglas
> Sent: Thursday, August 11, 2011 1:23 PM
> To: kernelnewbies@xxxxxxxxxxxxxxxxx
> Subject: SYSLOG_ACTION_READ_ALL question
> 
> Hello all,
> 
> I'm trying to figure out why the do_syslog code in kernel/printk.c is
> using put_user instead of copy_to_user.
> 

I *THINK* this has something to do with copy_to_user not being
well-behaved in other than process context and since printk() gets
called in all contexts, it wouldn't be a safe operation.
But don't take my word for it.





_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux