From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bob Peterson <rpeterso@redhat.com>
Date: Wed, 19 Oct 2016 11:38:15 -0400 (EDT)
Subject: [Cluster-devel] [DLM PATCH] DLM: Remove lock_sock to
	avoid	scheduling while atomic
In-Reply-To: <532967718.4100358.1476105592302.JavaMail.zimbra@redhat.com>
References: <532967718.4100358.1476105592302.JavaMail.zimbra@redhat.com>
Message-ID: <982458705.9550089.1476891495713.JavaMail.zimbra@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

----- 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