All of lore.kernel.org
 help / color / mirror / Atom feed
From: isdn@linux-pingi.de
To: Insu Yun <wuninsu@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: taesoo@gatech.edu, yeongjin.jang@gatech.edu, insu@gatech.edu
Subject: Re: [PATCH 2/2] isdn: correctly check failed allocation
Date: Thu, 15 Oct 2015 20:42:04 +0200	[thread overview]
Message-ID: <561FF37C.7070107@linux-pingi.de> (raw)
In-Reply-To: <1444926568-29572-2-git-send-email-wuninsu@gmail.com>

Hi Insu,

thanks for bringing up this issue again.
I thought I did fix this a year ago, but seems it did not managed to
sent it upstream.

The patch do not fix this completly, since it will drop the original skb
from the L2 I frame queue, so the transmission would lost an I-FRAME,
which is not allowed by the protocol.

The format of the new lines is wrong, you need to use TAB.


Best regards
Karsten

Am 15.10.2015 um 18:29 schrieb Insu Yun:
> Since skb_clone is memory allocation, it could be failed when lack of resource.
> Therefore, return value of skb_clone needs to be checked and handle error.
> 
> Signed-off-by: Insu Yun <wuninsu@gmail.com>
> ---
>  drivers/isdn/mISDN/layer2.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/isdn/mISDN/layer2.c b/drivers/isdn/mISDN/layer2.c
> index 949cabb..888c610 100644
> --- a/drivers/isdn/mISDN/layer2.c
> +++ b/drivers/isdn/mISDN/layer2.c
> @@ -1509,6 +1509,12 @@ l2_pull_iqueue(struct FsmInst *fi, int event, void *arg)
>  	}
>  
>  	nskb = skb_clone(skb, GFP_ATOMIC);
> +  if (!nskb) {
> +			printk(KERN_WARNING "%s: no skb mem in %s\n",
> +			       mISDNDevName4ch(&l2->ch), __func__);
> +			return;
> +  }
> +
>  	p1 = skb_headroom(nskb);
>  	if (p1 >= i)
>  		memcpy(skb_push(nskb, i), header, i);
> 


  reply	other threads:[~2015-10-15 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 16:29 [PATCH 1/2] isdn: correctly check failed allocation Insu Yun
2015-10-15 16:29 ` [PATCH 2/2] " Insu Yun
2015-10-15 18:42   ` isdn [this message]
2015-10-16  6:32   ` David Miller

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=561FF37C.7070107@linux-pingi.de \
    --to=isdn@linux-pingi.de \
    --cc=insu@gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=taesoo@gatech.edu \
    --cc=wuninsu@gmail.com \
    --cc=yeongjin.jang@gatech.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.