linux-kernel - Re: [PATCH] LinuxPPS (with new syscalls API)

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1182855427.12109.203.camel@pmac.infradead.org>
Date:	Tue, 26 Jun 2007 11:57:07 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Rodolfo Giometti <giometti@...eenne.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] LinuxPPS (with new syscalls API)

On Tue, 2007-06-26 at 12:06 +0200, Rodolfo Giometti wrote:
> Hello,
> 
> here my new version of LinuxPPS with a new syscalls API.
> 
> Please take a look at this new patch and report any
> suggestions/modifications so I can prepare a proper patch for kernel
> inclusion.

Your syscalls blindly dereference userspace pointers instead of using
copy_{to,from} user.

Why did you split all your syscalls into two functions?

s/__FUNCTION__/__func__/

s/antennas/antennae/

You seem to have added debugging messages mentioning 'serial8250' into
serial_core.h

You added <linux/pps.h> with #ifdef __KERNEL__ in it, but didn't export
it to userspace. Why?

Your structures for userspace communication look OK -- I don't think you
need special 32/64 compatibility for them. You do need it for the
'struct timespec' in sys_time_pps_fetch() though.

Must we have the ioctl-like interface to sys_time_pps_cmd()? If the
second argument is always 'struct pps_source_data_s *', why does the
syscall pretend it's 'void *'?

-- 
dwmw2

-
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/