[Bug 685072] New: memory: map(READ)/unmap clears the READONLY status

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=685072
  GStreamer | gstreamer (core) | 1.0.0

           Summary: memory: map(READ)/unmap clears the READONLY status
    Classification: Platform
           Product: GStreamer
           Version: 1.0.0
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: olivier.crete at ocrete.ca
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=225359)
 View: https://bugzilla.gnome.org/attachment.cgi?id=225359
 Review: https://bugzilla.gnome.org/review?bug=685072&attachment=225359

Patch to check the readonly flag on lock

Currently, if one locks and unlocks a GstMiniObject in read-mode, the read-only
status is cleared.. As read-only is only a read lock with a count of one..

After discussion with Wim, let's explicitly check the readonly flag.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.