linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: David Miller <davem@davemloft.net>
Cc: vishal@chelsio.com, nhorman@tuxdriver.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2 net-next] cxgb3/l2t: Fix undefined behaviour and use struct_size() helper
Date: Mon, 1 Apr 2019 17:36:05 -0500	[thread overview]
Message-ID: <a835d790-874b-1fdb-2497-2e5ebf5725eb@embeddedor.com> (raw)
In-Reply-To: <20190401.150215.729449280275163138.davem@davemloft.net>



On 4/1/19 5:02 PM, David Miller wrote:
> From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
> Date: Fri, 29 Mar 2019 10:26:16 -0500
> 
>> Hi all,
>>
>> This patchset aims to fix an undefined behaviour when using a zero-sized
>> array and, add the use of the struct_size() helper in kvzalloc().
>>
>> You might consider the first patch in this series for stable.
>>
>> More details in the commit logs.
> 
> Series applied, honestly I don't think this is -stable material.
> 

Okay.

> And if it was you should have targetted 'net' instead of 'net-next'.
> 

Got it.

Thanks, Dave.
--
Gustavo

      reply	other threads:[~2019-04-01 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 15:26 [PATCH 0/2 net-next] cxgb3/l2t: Fix undefined behaviour and use struct_size() helper Gustavo A. R. Silva
2019-03-29 15:27 ` [PATCH 1/2 net-next] cxgb3/l2t: Fix undefined behaviour Gustavo A. R. Silva
2019-03-29 15:28 ` [PATCH 2/2 net-next] cxgb3/l2t: Use struct_size() in kvzalloc() Gustavo A. R. Silva
2019-04-01 22:02 ` [PATCH 0/2 net-next] cxgb3/l2t: Fix undefined behaviour and use struct_size() helper David Miller
2019-04-01 22:36   ` Gustavo A. R. Silva [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=a835d790-874b-1fdb-2497-2e5ebf5725eb@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vishal@chelsio.com \
    /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).