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

ASF GitHub Bot commented on HADOOP-18490:
-----------------------------------------

FuzzingTeam opened a new pull request, #5001:
URL: https://github.com/apache/hadoop/pull/5001

   ### Description of PR
   JIRA: [HADOOP-18490](https://issues.apache.org/jira/browse/HADOOP-18490)
   
   ### How was this patch tested?
   Added a new value set in the test class `TestDecodingValidator` to verify 
the code change.
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> The check logic for erasedIndexes in XORRawDecoder is buggy
> -----------------------------------------------------------
>
>                 Key: HADOOP-18490
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18490
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.3.4
>            Reporter: FuzzingTeam
>            Priority: Major
>              Labels: pull-request-available
>
> In the method _doDecode_ of class {_}XORRawDecoder{_}, the code does not 
> handle all the erased and null marked locations in the array ({_}inputs{_}) 
> but only skips the first erased location ({_}erasedIndexes[0]{_}). The 
> missing handling results in an unhandled NullPointerException.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to