linux-kernel - accessing file operations directly in the kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 6 Nov 2008 22:39:59 +0000
From:	andy <rootstrap@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: accessing file operations directly in the kernel

Hi,

I am dealing with an interesting situation, which I have to access a
serial device driver
from the kernel space. I tried to use sys_open, sys_ioctl ... but
there is a problem
with the file descriptors.  Now, I started using direct calls to the
drivers functions
driver_open, driver_ioctl... passing the *inode from user_path_walk(),
but it doesn't
seem that works right. This serial device is going to be used only
from the other
module that runs in the kernel.

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