From: Li Zefan <lizefan@huawei.com>
To: <xuejiufei@huawei.com>
Cc: <oleg@redhat.com>, <tj@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: call_usermodehelper() returns -513 when ocfs2 umounting filesystems
Date: Tue, 30 Jul 2013 17:23:42 +0800 [thread overview]
Message-ID: <51F7861E.5050903@huawei.com> (raw)
In-Reply-To: <51F77E7D.20608@huawei.com>
On 2013/7/30 16:51, Xue jiufei wrote:
> 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 the filesystem, it
>> returns the same error.
>> And at the same time, there's another kworker thread which is
>> sending messages to other nodes always return return errno
>> -512(ERESTARTSYS). So I think these two threads may have
>> pending signals remain.
>> This error can not reproduced any longer. Has any ideas?
You should have made the question more clear, and that is:
How is it possible that a workqueue kernel thread has pending signals?
>>
>> The log is as follows:
>> [58463.684504] (kworker/u:1,17332,0):o2net_send_tcp_msg:1332 ERROR: sendmsg returned -512 instead of 104
>> [58915.213299] ocfs2: Error -513 running user helper "/usr/sbin/ocfs2_hb_ctl -K -u A5FD0ED8733D4F9C98D23B326AD7DE10"
>> [59406.443615] ocfs2: Error -513 running user helper "/usr/sbin/ocfs2_hb_ctl -K -u A5FD0ED8733D4F9C98D23B326AD7DE10"
>>
next prev parent reply other threads:[~2013-07-30 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 7:30 call_usermodehelper() returns -513 when ocfs2 umounting filesystems Xue jiufei
2013-07-30 8:51 ` Xue jiufei
2013-07-30 9:23 ` Li Zefan [this message]
2013-07-30 12:58 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F7861E.5050903@huawei.com \
--to=lizefan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tj@kernel.org \
--cc=xuejiufei@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox