summaryrefslogtreecommitdiffstats
path: root/net/rds
diff options
context:
space:
mode:
authorAndy Grover <andy.grover@oracle.com>2010-03-29 17:10:01 -0700
committerAndy Grover <andy.grover@oracle.com>2010-09-08 18:12:22 -0700
commita40aa9233aa22d69212d02f92e5b607bd4d658f4 (patch)
treef8c60fc02cb5ab58ea47fe5d381c140074149bbc /net/rds
parentfcc5450c6386526034edc437e4cb2c67a6fdd7e9 (diff)
downloadlinux-a40aa9233aa22d69212d02f92e5b607bd4d658f4.tar.gz
linux-a40aa9233aa22d69212d02f92e5b607bd4d658f4.tar.bz2
linux-a40aa9233aa22d69212d02f92e5b607bd4d658f4.zip
RDS: Do wait_event_interruptible instead of wait_event
Can't see a reason not to allow signals to interrupt the wait. Signed-off-by: Andy Grover <andy.grover@oracle.com>
Diffstat (limited to 'net/rds')
-rw-r--r--net/rds/message.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/net/rds/message.c b/net/rds/message.c
index 9122b5392111..4cb1ed704153 100644
--- a/net/rds/message.c
+++ b/net/rds/message.c
@@ -399,14 +399,14 @@ int rds_message_inc_copy_to_user(struct rds_incoming *inc,
*/
void rds_message_wait(struct rds_message *rm)
{
- wait_event(rds_message_flush_waitq,
+ wait_event_interruptible(rds_message_flush_waitq,
!test_bit(RDS_MSG_MAPPED, &rm->m_flags));
}
void rds_message_unmapped(struct rds_message *rm)
{
clear_bit(RDS_MSG_MAPPED, &rm->m_flags);
- wake_up(&rds_message_flush_waitq);
+ wake_up_interruptible(&rds_message_flush_waitq);
}
EXPORT_SYMBOL_GPL(rds_message_unmapped);