Subject: Re: IOCTL implementation and kernel/userland addresses
To: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 02/14/2005 10:45:57
--WYTEVAkct0FjGQmd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 14, 2005 at 12:51:07PM +0900, YAMAMOTO Takashi wrote:
> > > > > Would proc still be NULL if the IOCTL is called from a kernel thr=
ead ?
> > > >=20
> > > > We're making the semantics of such a call up as we go along. Howeve=
r I=20
> > > > think that passing proc =3D=3D NULL if the secondary addresses are =
in kernel=20
> > > > space is reasonable.
> > >=20
> > > Won't this cause problems if the ioctl wants to sleep ?
> >=20
> > Hmm.... Yes.
>=20
> what's a problem if it sleeps?

Ahh, I was mistakenly thinking that ltsleep wants the proc pointer, and=20
thus NULL would have problems. As it doesn't, we should be fine.

Take care,

Bill

--WYTEVAkct0FjGQmd
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFCEPHlWz+3JHUci9cRAq+4AJ49DrBEIh7ezc6F1TSaGdt8DQ2hwACeN3Jv
GAfv0O0B5r58cG5koDV8W48=
=eM4O
-----END PGP SIGNATURE-----

--WYTEVAkct0FjGQmd--