Commit a40aa923 authored by Andy Grover's avatar Andy Grover

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: default avatarAndy Grover <andy.grover@oracle.com>
parent fcc5450c
...@@ -399,14 +399,14 @@ int rds_message_inc_copy_to_user(struct rds_incoming *inc, ...@@ -399,14 +399,14 @@ int rds_message_inc_copy_to_user(struct rds_incoming *inc,
*/ */
void rds_message_wait(struct rds_message *rm) 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)); !test_bit(RDS_MSG_MAPPED, &rm->m_flags));
} }
void rds_message_unmapped(struct rds_message *rm) void rds_message_unmapped(struct rds_message *rm)
{ {
clear_bit(RDS_MSG_MAPPED, &rm->m_flags); 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); EXPORT_SYMBOL_GPL(rds_message_unmapped);
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment