Hi Junxiao
On 2014/9/3 9:38, Junxiao Bi wrote:
> Hi Jiufei,
>
> On 09/02/2014 05:03 PM, Xue jiufei wrote:
>> Hi, Dave
>> On 2014/9/2 7:51, Dave Chinner wrote:
>>> On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
>>>> The patch trys to so
Hi, Dave
On 2014/9/3 9:02, Dave Chinner wrote:
> On Tue, Sep 02, 2014 at 05:03:27PM +0800, Xue jiufei wrote:
>> Hi, Dave
>> On 2014/9/2 7:51, Dave Chinner wrote:
>>> On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
>>>> The patch trys to solve on
Hi, Dave
On 2014/9/2 7:51, Dave Chinner wrote:
> On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
>> The patch trys to solve one deadlock problem caused by cluster
>> fs, like ocfs2. And the problem may happen at least in the below
>> situations:
>> 1)Recei
Hi, Dave
On 2014/9/2 7:51, Dave Chinner wrote:
On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2. And the problem may happen at least in the below
situations:
1)Receiving a connect message from other nodes
Hi, Dave
On 2014/9/3 9:02, Dave Chinner wrote:
On Tue, Sep 02, 2014 at 05:03:27PM +0800, Xue jiufei wrote:
Hi, Dave
On 2014/9/2 7:51, Dave Chinner wrote:
On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2
Hi Junxiao
On 2014/9/3 9:38, Junxiao Bi wrote:
Hi Jiufei,
On 09/02/2014 05:03 PM, Xue jiufei wrote:
Hi, Dave
On 2014/9/2 7:51, Dave Chinner wrote:
On Fri, Aug 29, 2014 at 05:57:22PM +0800, Xue jiufei wrote:
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2
Hi Viro & Andraw
Could you help review this patch?
Thanks.
xuejiufei
On 2014/8/29 17:57, Xue jiufei wrote:
> The patch trys to solve one deadlock problem caused by cluster
> fs, like ocfs2. And the problem may happen at least in the below
> situations:
> 1)Receiving a connect me
Hi Viro Andraw
Could you help review this patch?
Thanks.
xuejiufei
On 2014/8/29 17:57, Xue jiufei wrote:
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2. And the problem may happen at least in the below
situations:
1)Receiving a connect message from other nodes
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2. And the problem may happen at least in the below
situations:
1)Receiving a connect message from other nodes, node queues a
work_struct o2net_listen_work.
2)o2net_wq processes this work and calls sock_alloc() to allocate
The patch trys to solve one deadlock problem caused by cluster
fs, like ocfs2. And the problem may happen at least in the below
situations:
1)Receiving a connect message from other nodes, node queues a
work_struct o2net_listen_work.
2)o2net_wq processes this work and calls sock_alloc() to allocate
On 2013/7/30 15:30, Xue jiufei wrote:
> Hi,
> We have encountered an error when umounting ocfs2 filesystems.
> Function ocfs2_leave_group() calls call_usermodehelper() to stop
> heartbeat thread, but it returns -513(ERESTARTNOINTR) in one test.
> And after that error, every
Hi,
We have encountered an error when umounting ocfs2 filesystems.
Function ocfs2_leave_group() calls call_usermodehelper() to stop
heartbeat thread, but it returns -513(ERESTARTNOINTR) in one test.
And after that error, every times umounting the filesystem, it
returns the same error.
And at the
Hi,
We have encountered an error when umounting ocfs2 filesystems.
Function ocfs2_leave_group() calls call_usermodehelper() to stop
heartbeat thread, but it returns -513(ERESTARTNOINTR) in one test.
And after that error, every times umounting the filesystem, it
returns the same error.
And at the
On 2013/7/30 15:30, Xue jiufei wrote:
Hi,
We have encountered an error when umounting ocfs2 filesystems.
Function ocfs2_leave_group() calls call_usermodehelper() to stop
heartbeat thread, but it returns -513(ERESTARTNOINTR) in one test.
And after that error, every times umounting
14 matches
Mail list logo
