Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <58768627.1224178544684.JavaMail.jira@brutus>
Date: Thu, 16 Oct 2008 10:35:44 -0700 (PDT)
From: "Pete Wyckoff (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
 safe and can cause segfaults and corruptions
In-Reply-To: <2095472165.1223859044184.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Wyckoff updated HADOOP-4398:
---------------------------------

    Status: Open  (was: Patch Available)

> fuse-dfs per FD context is not thread safe and can cause segfaults and corruptions
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-4398
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4398
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fuse-dfs
>    Affects Versions: 0.20.0
>            Reporter: Pete Wyckoff
>            Assignee: Pete Wyckoff
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4398.1.txt
>
>
> this affects dfs_read and dfs_write and dfs_open dfs_release.
> people have seen corruptions in 0.18.1 on reads - hadoop-4397.
> In 0.19 since there is no global DFS handle, it is slightly different, but the same principles need to be applied and make the per FD context data (ie ptr to DFS, read buffer, ...) thread safe.
> I can't think of a way to add a reliable test case for this in the current framework, but should be sure to assert pre/post conditions wherever possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.