Date: Thu, 06 Jul 2006 15:53:43 -0600 From: Scott Long <scottl@samsco.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/amd64/linux32 syscalls.master src/sys/compat/linux linux_ioctl.c src/sys/i386/linux syscalls.master Message-ID: <44AD8667.9090600@samsco.org> In-Reply-To: <200607062142.k66LgaoV050809@repoman.freebsd.org> References: <200607062142.k66LgaoV050809@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > jhb 2006-07-06 21:42:36 UTC > > FreeBSD src repository > > Modified files: > sys/amd64/linux32 syscalls.master > sys/compat/linux linux_ioctl.c > sys/i386/linux syscalls.master > Log: > - Protect the list of linux ioctl handlers with an sx lock. > - Hold Giant while calling linux ioctl handlers for now as they aren't all > known to be MPSAFE yet. > - Mark linux_ioctl() MPSAFE. > > Revision Changes Path > 1.15 +1 -1 src/sys/amd64/linux32/syscalls.master > 1.137 +17 -0 src/sys/compat/linux/linux_ioctl.c > 1.72 +1 -1 src/sys/i386/linux/syscalls.master Why not add the small bit of infrastucture so that modules can declare their handlers as MPSAFE or not? There are certainly some drivers that would benefit from this. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44AD8667.9090600>