From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [DLM PATCH] DLM: Remove lock_sock to avoid scheduling while atomic
Date: Wed, 19 Oct 2016 11:38:15 -0400 (EDT) [thread overview]
Message-ID: <982458705.9550089.1476891495713.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <532967718.4100358.1476105592302.JavaMail.zimbra@redhat.com>
----- Original Message -----
| Hi,
|
| Before this patch, functions save_callbacks and restore_callbacks
| called function lock_sock and release_sock to prevent other processes
| from messing with the struct sock while the callbacks were saved and
| restored. However, function add_sock calls write_lock_bh prior to
| calling it save_callbacks, which disables preempts. So the call to
| lock_sock would try to schedule when we can't schedule.
|
| Signed-off-by: Bob Peterson <rpeterso@redhat.com>
| ---
Hi Dave,
Same question, different patch: Any word on this patch from 10 October?
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2016-10-19 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1791542555.4100267.1476105550995.JavaMail.zimbra@redhat.com>
2016-10-10 13:19 ` [Cluster-devel] [DLM PATCH] DLM: Remove lock_sock to avoid scheduling while atomic Bob Peterson
2016-10-19 15:38 ` Bob Peterson [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=982458705.9550089.1476891495713.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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 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.