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: Thu, 13 Jan 2005 09:01:28 -0500 [thread overview]
Message-ID: <41E67F38.6060203@RedHat.com> (raw)
In-Reply-To: <1105576681.14443.100.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>on den 12.01.2005 Klokka 14:11 (-0500) skreiv Steve Dickson:
>
>
>
>>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.....
>>
>>
>
>No! Those extra checks are neither necessary, nor are they even correct!
>I repeat what I said in my earlier mail:
>
> - The change to nfs_wait_event() converts it into an
> unconditional uninterruptible sleep. That means you can never
> "kill -9" out of waiting for the core dump to finish in case the
> server crashes!
>
>
By adding the PF_DUMPCORE check to rpc_clnt_sigmask() (as you suggested)
I thought I had taken care of this problem... but now I realize the
check in nfs_wait_event()
is the real issue... sorry for making you swing that clue bat twice!! :)
> - The loop you add to __rpc_execute() is pointless: The signal
> that caused your process to wake up is neither cleared nor
> masked, so when it later tries to block (such as when waiting
> for a reply from the server), that process will just find itself
> immediately woken up again by the same signal.
>
>
I do understand this point.... and I *thought* I had addressed it by
making __rpc_execute()
temporary ignoring signals and having nfs_wait_event () call
wait_event() instead
of wait_event_interruptible().....
>As for myself, I'm getting full coredumps when I apply the 2 line patch
>I sent you. The appended testcase works every time:
>
>
hmm.... something is amiss.... because I'm definitely not see this....
but I'll keep digging...
thanks!
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-13 14:01 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
2005-01-13 0:38 ` Trond Myklebust
2005-01-13 14:01 ` Steve Dickson [this message]
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=41E67F38.6060203@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox