spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcelo Vanzin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-13684) Possible unsafe bytesRead increment in StreamInterceptor
Date Fri, 04 Mar 2016 21:24:40 GMT

    [ https://issues.apache.org/jira/browse/SPARK-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180554#comment-15180554
] 

Marcelo Vanzin commented on SPARK-13684:
----------------------------------------

If switching to AtomicLong gets rid of the warning, that's fine.

> Possible unsafe bytesRead increment in StreamInterceptor
> --------------------------------------------------------
>
>                 Key: SPARK-13684
>                 URL: https://issues.apache.org/jira/browse/SPARK-13684
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: holdenk
>            Priority: Trivial
>
> We unsafely increment a volatile (bytesRead) in a call back, if two call backs are triggered
we may under count bytesRead. This issue was found using coverity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message