public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Xue jiufei <xuejiufei@huawei.com>
Cc: oleg@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: call_usermodehelper() returns -513 when ocfs2 umounting filesystems
Date: Tue, 30 Jul 2013 08:58:34 -0400	[thread overview]
Message-ID: <20130730125834.GA12016@htj.dyndns.org> (raw)
In-Reply-To: <51F77E7D.20608@huawei.com>

On Tue, Jul 30, 2013 at 04:51:09PM +0800, Xue jiufei wrote:
> The kernel version is 3.0.58.

That's way too old for upstream to do any meaningful debugging without
more specific information.  Kernel threads usually don't deal with
signals but there are a handful weird places in kernel which make use
of actual signals to affect the control flow.  ISTR modifying some so
that it's not too crazy but I could be misremembering....

Thanks.

-- 
tejun

      parent reply	other threads:[~2013-07-30 12:58 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
2013-07-30 12:58   ` Tejun Heo [this message]

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=20130730125834.GA12016@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --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