From: David Miller <davem@davemloft.net>
To: wuninsu@gmail.com
Cc: hariprasad@chelsio.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, taesoo@gatech.edu,
yeongjin.jang@gatech.edu, insu@gatech.edu, changwoo@gatech.edu
Subject: Re: [PATCH] cxgb4: correctly handling failed allocation
Date: Mon, 04 Jan 2016 17:19:00 -0500 (EST) [thread overview]
Message-ID: <20160104.171900.1006206453660470786.davem@davemloft.net> (raw)
In-Reply-To: <1451427611-32338-1-git-send-email-wuninsu@gmail.com>
From: Insu Yun <wuninsu@gmail.com>
Date: Tue, 29 Dec 2015 17:20:11 -0500
> Since t4_alloc_mem can be failed in memory pressure,
> if not properly handled, NULL dereference could be happened.
>
> Signed-off-by: Insu Yun <wuninsu@gmail.com>
Applied.
prev parent reply other threads:[~2016-01-04 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 22:20 [PATCH] cxgb4: correctly handling failed allocation Insu Yun
2016-01-04 22:19 ` David Miller [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=20160104.171900.1006206453660470786.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=changwoo@gatech.edu \
--cc=hariprasad@chelsio.com \
--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 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).