Messages in this thread | | | Date | Thu, 02 Apr 2015 14:08:50 -0400 (EDT) | Subject | Re: [PATCHv2 3/6] rds: check for excessive looping in rds_send_xmit | From | David Miller <> |
| |
From: Sowmini Varadhan <sowmini.varadhan@oracle.com> Date: Thu, 2 Apr 2015 10:19:37 -0400
> @@ -177,6 +178,18 @@ int rds_send_xmit(struct rds_connection *conn) > > rm = conn->c_xmit_rm; > > + if (!rm) { > + same_rm = 0; > + } else { > + same_rm++; > + if (same_rm >= 4096) { > + printk_ratelimited(KERN_ERR "RDS: Stuck rm\n"); > + cond_resched(); > + ret = -EAGAIN; > + break; > + } > + } > +
I'm not accepting junk like this.
I want to know exactly how this situation can occur, in detail, and then and only then can we start to talk about more reasonable solutions to this bug.
This looks like a minimal effort hack to make a hang go away, and even more concerning is that a change like this is submitted with a commit message that is essentially empty.
Sorry, this is not acceptable.
| |