Subject: Re: IOCTL implementation and kernel/userland addresses
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 02/07/2005 10:59:53
--vmttodhTwj0NAgWp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Feb 07, 2005 at 07:40:36PM +0100, Manuel Bouyer wrote:
> On Mon, Feb 07, 2005 at 10:01:14AM -0800, Bill Studenmund wrote:
> > > Would proc still be NULL if the IOCTL is called from a kernel thread ?
> >=20
> > We're making the semantics of such a call up as we go along. However I=
=20
> > think that passing proc =3D=3D NULL if the secondary addresses are in k=
ernel=20
> > space is reasonable.
>=20
> Won't this cause problems if the ioctl wants to sleep ?
Hmm.... Yes.
Now that I look at it more, we might add an extra flag to the file=20
descriptor flags, as they get passed in as the "fflag" parameter. There's=
=20
plenty of space, we just need to document it. :-)
Take care,
Bill
--vmttodhTwj0NAgWp
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD8DBQFCB7qpWz+3JHUci9cRAtw0AJ4wH/nV2xgoycqYCpBru2UjTTpzFACglqXj
WeMfFX4pVr8wsLEPDao/qZE=
=TYfT
-----END PGP SIGNATURE-----
--vmttodhTwj0NAgWp--