two segfaults in ruby inotify extension library

Bug #736521 reported by Jeremy Fishman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libinotify-ruby (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: libinotify-ruby

Segfault #1 - Poor input type checking in rb_inotify_add_watch() throws a segfault when passed e.g. the nil object
Segfault #2 - Closing the inotify file descriptor in a separate thread may lead to fd reuse and segfault in rb_inotify_each_event

Supplied patch provides tests to trigger these bugs and
a) adds a type check in rb_inotify_add_watch()
b) sets the file descriptor to -1 in rb_inotify_close()
c) exits rb_inotify_each_event() when the file descriptor is invalidated

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libinotify-ruby 0.0.2-4
ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic x86_64
Architecture: amd64
Date: Wed Mar 16 15:59:26 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: libinotify-ruby

Revision history for this message
Jeremy Fishman (jeremy-r-fishman) wrote :
tags: added: patch
Revision history for this message
Dave Walker (davewalker) wrote :

Hi Jeremy, thanks for your patch.

Can I ask, did you author this patch, and have you made any progress trying to report this issue+patch upstream?

Thanks.

Revision history for this message
Jeremy Fishman (jeremy-r-fishman) wrote :

Hi Dave,

Yes, I authored the patch. I have just sent an email to the upstream author and will update here if they reply.

Revision history for this message
Jeremy Fishman (jeremy-r-fishman) wrote :

Still no reply from upstream.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.