From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4811E04A.2060205@domain.hid> Date: Fri, 25 Apr 2008 15:44:42 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4811D596.8070109@domain.hid> <2ff1a98a0804250612k6ba655f5mc92cb47a12f01d@domain.hid> In-Reply-To: <2ff1a98a0804250612k6ba655f5mc92cb47a12f01d@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [2.4.x PATCH] POSIX: Remove mutex/cond_init locking, fix NULL attribute List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai-core@domain.hid Gilles Chanteperdrix wrote: > On Fri, Apr 25, 2008 at 2:59 PM, Jan Kiszka wrote: >> Hi, >> >> trunk check-in #3369 did not just remove some "questionable critical >> sections", it also happen to fix two ugly bugs in the POSIX skin: The >> user was not able to pass NULL attributes down to mutex_init and >> cond_init. Find a backport of that patch for 2.4.x attached. > > I am using pthread_mutex_init and pthread_cond_init from user-space > with NULL attributes with pre 2.4 versions all the time, and never had > any problem. Maybe a x86-64 issue: __xn_access_ok() triggers here when you stuff in a NULL pointer. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux