From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: linux-sctp@vger.kernel.org, David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] [SCTP] Fix a type cast bug
Date: Fri, 16 May 2008 08:48:38 -0400 [thread overview]
Message-ID: <482D82A6.1060704@hp.com> (raw)
In-Reply-To: <482D4A8E.4090903@cn.fujitsu.com>
Gui
Gui Jianfeng wrote:
> Vlad,
>
> event_arg can never be the type of "struct sctp_chunk *"
> if the event_type is SCTP_EVENT_T_OTHER. This fix
> prevents from potential kernel crash by some misuse.
>
> Signed-off-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
> ---
> net/sctp/sm_sideeffect.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/net/sctp/sm_sideeffect.c b/net/sctp/sm_sideeffect.c
> index a4763fd..1b4bae9 100644
> --- a/net/sctp/sm_sideeffect.c
> +++ b/net/sctp/sm_sideeffect.c
> @@ -1072,7 +1072,8 @@ static int sctp_cmd_interpreter(sctp_event_t event_type,
> struct sctp_sackhdr sackh;
> int local_cork = 0;
>
> - if (SCTP_EVENT_T_TIMEOUT != event_type)
> + if (SCTP_EVENT_T_TIMEOUT != event_type &&
> + SCTP_EVENT_T_OTHER != event_type)
> chunk = (struct sctp_chunk *) event_arg;
>
> /* Note: This whole file is a huge candidate for rework.
This doesn't really fix the bug since the event_arg can be something else during
primitive events and you would still have a typecast issue.
This code is rather ugly, but if we are going to clean it up, we need to do right
and not band-aid to death.
As it is, NACK on this patch, since it doesn't solve the problem.
-vlad
prev parent reply other threads:[~2008-05-16 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 8:49 [PATCH] [SCTP] Fix a type cast bug Gui Jianfeng
2008-05-16 12:48 ` Vlad Yasevich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482D82A6.1060704@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).