sctp: do not return the transmit err back to sctp_sendmsg (66388f2c) · Commits · 戴 / test

Once a chunk is enqueued successfully, sctp queues can take care of it. Even if it is failed to transmit (like because of nomem), it should be put into retransmit queue. If sctp report this error to users, it confuses them, they may resend that msg, but actually in kernel sctp stack is in charge of retransmit it already. Besides, this error probably is not from the failure of transmitting current msg, but transmitting or retransmitting another msg's chunks, as sctp_outq_flush just tries to send out all transports' chunks. This patch is to make sctp_cmd_send_msg return avoid, and not return the transmit err back to sctp_sendmsg Fixes: ("sctp: only drop the reference on the datamsg after sending a msg") Signed-off-by:

Xin Long <lucien.xin@gmail.com> Signed-off-by:

David S. Miller <davem@davemloft.net>

net/sctp/sm_sideeffect.c

+5 −11

Original line number	Diff line number	Diff line
		@@ -1020,19 +1020,13 @@ static void sctp_cmd_t1_timer_update(struct sctp_association *asoc,
		* This way the whole message is queued up and bundling if
		* encouraged for small fragments.
		*/
		static int sctp_cmd_send_msg(struct sctp_association *asoc,
		static void sctp_cmd_send_msg(struct sctp_association *asoc,
		struct sctp_datamsg *msg, gfp_t gfp)
		{
		struct sctp_chunk *chunk;
		int error = 0;

		list_for_each_entry(chunk, &msg->chunks, frag_list) {
		error = sctp_outq_tail(&asoc->outqueue, chunk, gfp);
		if (error)
		break;
		}

		return error;
		list_for_each_entry(chunk, &msg->chunks, frag_list)
		sctp_outq_tail(&asoc->outqueue, chunk, gfp);
		}


		@@ -1709,7 +1703,7 @@ static int sctp_cmd_interpreter(sctp_event_t event_type,
		sctp_outq_cork(&asoc->outqueue);
		local_cork = 1;
		}
		error = sctp_cmd_send_msg(asoc, cmd->obj.msg, gfp);
		sctp_cmd_send_msg(asoc, cmd->obj.msg, gfp);
		break;
		case SCTP_CMD_SEND_NEXT_ASCONF:
		sctp_cmd_send_asconf(asoc);

Admin message