Re: Problem in calling System call [sys_mknod] in Kernel Module.

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

 



On Tue, 5 Oct 2004 18:27:09 +0100 (BST), Dinesh Ahuja
<mdlinux7@xxxxxxxxxxx> wrote:
> > This is what udev is for, and previously also devfs.
> > It has been done
> > in userspace properly using a daemon which handles
> > device creation in
> > a portable way - so it's not worth re-inventing the
> > wheel for just one
> > driver - but more to the point, it's icky and yucky
> > doing this in a
> > driver.
> 
> Thanks again Jon.

I'm just trying to be helpful. Sometimes I have something useful to say.

> I read very nice explanation that why we
> sys_call_table support has been stopped.

Your explaination is correct - it's difficult to protect the syscall
table and so this happened. Personally I think it would be nice to be
able to modify it more easily but that would require some redesign to
add the various protections necessary. For example when the next
exploit comes out which affects the vm syscalls I'd prefer a loadable
module fix.

(this is speaking as an occasional admin with production boxes kicking
around that we rely upon not needed to be rebooted every 5 minutes -
i.e. most so called "real world" users).

Cheers,

Jon.

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[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