From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] -o intr mount option prevents core dumps on 2.4 kernel
Date: Wed, 12 Jan 2005 14:11:59 -0500 [thread overview]
Message-ID: <41E5767F.40204@RedHat.com> (raw)
In-Reply-To: <1105554342.23943.1.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>===================================================================
>--- linux-2.4.28-rc1.orig/net/sunrpc/clnt.c
>+++ linux-2.4.28-rc1/net/sunrpc/clnt.c
>@@ -209,7 +209,7 @@ void rpc_clnt_sigmask(struct rpc_clnt *c
> unsigned long irqflags;
>
> /* Turn off various signals */
>- if (clnt->cl_intr) {
>+ if (clnt->cl_intr && !(current->flags & PF_DUMPCORE)) {
> struct k_sigaction *action = current->sig->action;
> if (action[SIGINT-1].sa.sa_handler == SIG_DFL)
> sigallow |= sigmask(SIGINT);
>
>
Well did you try just this? ;-)
Here is what I found.... just adding the PF_DUMPCORE rpc_clnt_sigmask()
no core was dropped
because __rpc_execute returned -ERESTARTSYS due to signalled() == TRUE.
When I added back the PF_DUMPCORE check to __rpc_execute(), only the
header of the core
was dropped because nfs_wait_event() returned -ERESTARTSYS because
signalled() == TRUE.
When I added back the PF_DUMPCORE to nfs_wait_event(), the entire core
was dropped.
So it appears to me that you need both checks.....
steved
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-01-12 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 18:31 [PATCH] -o intr mount option prevents core dumps on 2.4 kernel Steve Dickson
2005-01-07 17:14 ` Trond Myklebust
2005-01-11 19:36 ` Steve Dickson
2005-01-11 20:10 ` Trond Myklebust
2005-01-11 20:58 ` Steve Dickson
2005-01-11 21:59 ` Trond Myklebust
2005-01-12 18:18 ` Steve Dickson
2005-01-12 18:25 ` Trond Myklebust
2005-01-12 19:11 ` Steve Dickson [this message]
2005-01-13 0:38 ` Trond Myklebust
2005-01-13 14:01 ` Steve Dickson
2005-01-13 21:37 ` Steve Dickson
2005-01-14 2:57 ` Trond Myklebust
2005-01-14 19:52 ` Steve Dickson
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=41E5767F.40204@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.