Date: Sat, 29 Mar 2014 12:31:04 +0800 From: David Xu <davidxu@freebsd.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: src-committers@FreeBSD.org, mjg@FreeBSD.org, Don Lewis <truckman@FreeBSD.org>, svn-src-head@FreeBSD.org, kostikbel@gmail.com, svn-src-all@FreeBSD.org Subject: Re: svn commit: r263755 - head/sys/kern Message-ID: <53364C88.5080706@freebsd.org> In-Reply-To: <20140329041441.GD29296@dft-labs.eu> References: <53351627.9000703@freebsd.org> <201403281613.s2SGDKpk010871@gw.catspoiler.org> <20140329025602.GB29296@dft-labs.eu> <5336396E.7000801@freebsd.org> <20140329032513.GC29296@dft-labs.eu> <53364369.10500@freebsd.org> <20140329041441.GD29296@dft-labs.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014/03/29 12:14, Mateusz Guzik wrote: > I asked if multpiple concurrent calls to fsetown(.., &pointer) could > result in some corruption in the kernel - if they could, we would have > a problem in the future. I decided to read the code once more and > fsetown seems to be safe in this regard after all and with that in > mind the patch looks good to me. This thread is too long already, so > I'm stepping down on this one in case there are some futher concerns. This thread is really long, but things must be clarified, so it was not long enough. :-) Previously I supposed you had read the fsetown code, if not, I was wrong, lol.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53364C88.5080706>