Re: [Xenomai-core] [git pull] RTDM: Fix potential NULL pointer dereference

[Jan Kiszka <jan.kiszka@domain.hid>]

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Gilles Chanteperdrix wrote:
>>>>> Jan Kiszka wrote:
>>>>>> Gilles Chanteperdrix wrote:
>>>>>>> Jan Kiszka wrote:
>>>>>>>> The following changes since commit 6b3e8f2e5c69397814cb2f4029cdfbaff16e113e:
>>>>>>>>   Gilles Chanteperdrix (1):
>>>>>>>>         doc: regenerate
>>>>>>>>
>>>>>>>> are available in the git repository at:
>>>>>>>>
>>>>>>>>   git://git.xenomai.org/xenomai-jki.git for-upstream
>>>>>>>>
>>>>>>>> Unfortunately too late for 2.5.2, fortunately only relevant if something
>>>>>>>> else went wrong in create_instance (ENOMEM or application error).
>>>>>>>>
>>>>>>>> Wolfgang Mauerer (1):
>>>>>>>>       RTDM: Fix potential NULL pointer dereference
>>>>>>>>
>>>>>>>>  ksrc/skins/rtdm/core.c |    2 +-
>>>>>>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>>>>
>>>>>>> Was not there any plan to remove this code and have a more "posix
>>>>>>> compliant" close? I thought this had been merged?
>>>>>> Yes. But that requires more work than it would have been appropriate for
>>>>>> 2.5.2.
>>>>> Ok, but could we have it for 2.5.3?
>>>>>
>>>> Will see what I can do (no budget for this, so no promise).
>>> The patches are floating around for some time (I was in CC of the mail
>>> Philippe sent you about this some time ago), I guess some testing is
>>> needed, this is why you need some time? Could we help with this testing?
>>>
>> Then I totally lost track of this. What series are you referring to?
> 
> A (private) mail entitled "Re: RTDM close() refactoring" from Philippe,
> with in fact, a unique patch.
> 

Ah, now I found it. That discussion ended last September with a "Don't
bother yet" by Philippe as he said you pointed out some remaining issues
/wrt POSIX compliance. So I stopped bothering.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux