[Bugs] [Bug 1199075] iobuf: Ref should be taken on iobuf through proper functions.
bugzilla at redhat.com
bugzilla at redhat.com
Thu Apr 2 10:08:40 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1199075
--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9812 committed in master by Vijay Bellur
(vbellur at redhat.com)
------
commit 10b4ecb85c5009c6c7b9422bd5299ba43d8448a1
Author: Raghavendra Talur <rtalur at redhat.com>
Date: Thu Mar 5 18:19:30 2015 +0530
iobuf: Do not call __iobuf_ref directly
iobuf_get will be creating the iobuf and
hence lock is not necessary to increment ref.
However, it is a good practice to call
iobuf_ref instead of __iobuf_ref so that
we have a single point to get refs and
this can be used later to do mem
accounting etc.
Change-Id: I1fd328c3c463c23fd5f6df505ccb5c86f6207f28
BUG: 1199075
Signed-off-by: Raghavendra Talur <rtalur at redhat.com>
Reviewed-on: http://review.gluster.org/9812
Reviewed-by: Niels de Vos <ndevos at redhat.com>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wGJ5ieNcEG&a=cc_unsubscribe
More information about the Bugs
mailing list