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] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703090737230.1617@CPE00045a9c397f-CM001225dbafb6>
Date:	Fri, 9 Mar 2007 07:48:47 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	linux-kernel@...r.kernel.org
Subject: Re: any thoughts yet on a "generic" ioctl.h?

On Fri, 9 Mar 2007, Stefan Richter wrote:

> Robert P. J. Day wrote:
> > if someone can't immediately see what i'm trying
> > to do given the previously-posted patch, then they shouldn't be
> > commenting on it one way or the other.
>
> I'm not sure if you are addressing me too.  Just to clarify:  I
> wasn't commenting on the patch, I only commented on what I quoted in
> my reply.

sorry, i worded that *really* badly.  i didn't mean to imply that
*you* were incapable of understanding what the patch represented --
i've seen enough of your posts to appreciate your technical expertise.

all i want to know is if the proposed patch making
include/asm-generic/ioctl.h more flexible is even *theoretically* a
feasible thing to do, or whether anyone on this list would have any
howling objections to it.

not only that, but i would *prefer* to submit just that file as a
first patch all by itself since, again theoretically, it shouldn't
break anything and i'd like to verify that first before trying to
simplify any of the arch-specific ioctl.h files one at a time.

as it is, the number of arch-specific ioctl.h files that could
potentially be made *much* shorter are for the arches:

  mips
  parisc
  alpha
  sparc
  sparc-64
  powerpc

all the rest simply include asm-generic/ioctl.h directly.

rday

p.s.  for those who may have come in late, the proposed new
asm-generic/ioctl.h file would allow an includer to override any or
all of:

  _IOC_SIZEBITS
  _IOC_DIRBITS
  _IOC_NONE
  _IOC_WRITE
  _IOC_READ

AFAICT, those are the only differences across the entire spectrum of
ioctl.h files.  if there's something i've missed, feel free to let me
know.

--
========================================================================
Robert P. J. Day Linux Consulting, Training and Annoying Kernel
Pedantry Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ