linux-kernel - Re: [PATCHv2 3/5] sctp: extend socket API for sched configuration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CB56E7F.3030908@cn.fujitsu.com>
Date:	Wed, 13 Oct 2010 16:31:59 +0800
From:	Shan Wei <shanwei@...fujitsu.com>
To:	Yaogong Wang <ywang15@...u.edu>
CC:	linux-sctp@...r.kernel.org,
	Vlad Yasevich <vladislav.yasevich@...com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 3/5] sctp: extend socket API for sched configuration

Yaogong Wang wrote, at 09/12/2010 09:13 AM:
> Augment SCTP socket API with a new socket option SCTP_SCHED
> to choose and configure multistream scheduling algorithm.
> 
> Signed-off-by: Yaogong Wang <ywang15@...u.edu>
> ---
>  include/net/sctp/structs.h |    4 ++
>  include/net/sctp/user.h    |   19 ++++++++++
>  net/sctp/outqueue.c        |    4 ++
>  net/sctp/sm_sideeffect.c   |   45 +++++++++++++++++++++++--
>  net/sctp/socket.c          |   80 ++++++++++++++++++++++++++++++++++++++++++++
>  5 files changed, 149 insertions(+), 3 deletions(-)
> 
> diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
> index 52af764..1a76417 100644
> --- a/include/net/sctp/structs.h
> +++ b/include/net/sctp/structs.h
> @@ -333,6 +333,8 @@ struct sctp_sock {
> 
>  	/* Multistream scheduling */
>  	const struct sctp_sched_ops *sched_ops;
> +	__u16 sched_config_len;
> +	void *sched_config;
> 
>  	struct sctp_initmsg initmsg;
>  	struct sctp_rtoinfo rtoinfo;
> @@ -1173,6 +1175,8 @@ struct sctp_outq {
> 
>  	/* Multistream scheduling */
>  	const struct sctp_sched_ops *sched_ops;
> +	__u16 sched_config_len;
> +	void *sched_config;

Why did you take these two fields into sctp_sock and sctp_outq?
These two fields between sctp_sock and sctp_outq has same role,
we can only defined in one place.
How about using sctp_sk(sctp_outq->asoc->base.sk) to access these two
fields?


-- 
Best Regards
-----
Shan Wei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/