From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>,
Kunwu Chan <chentao@kylinos.cn>
Cc: <jesse.brandeburg@intel.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<jeffrey.t.kirsher@intel.com>, <shannon.nelson@amd.com>,
<kunwu.chan@hotmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v4 iwl-next] i40e: Use correct buffer size in i40e_dbg_command_read
Date: Thu, 7 Dec 2023 15:25:47 -0800 [thread overview]
Message-ID: <92e5cc01-e8b3-b6d2-e884-3d6bd001f0d0@intel.com> (raw)
In-Reply-To: <2a0f3c2a-71fe-4c79-8827-e53088bf3761@intel.com>
On 12/6/2023 4:40 AM, Alexander Lobakin wrote:
> From: Kunwu Chan <chentao@kylinos.cn>
> Date: Tue, 5 Dec 2023 17:58:44 +0800
>
>> The size of "i40e_dbg_command_buf" is 256, the size of "name"
>> depends on "IFNAMSIZ", plus a null character and format size,
>> the total size is more than 256.
>>
>> Improve readability and maintainability by replacing a hardcoded string
>> allocation and formatting by the use of the kasprintf() helper.
>>
>> Fixes: 02e9c290814c ("i40e: debugfs interface")
>> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
>> Suggested-by: Simon Horman <horms@kernel.org>
>> Suggested-by: Alexander Lobakin <aleksander.lobakin@intel.com>
>
> Your Signed-off-by must be the last tag in the block.
> Perhaps the maintainer could fix it when taking, so that you wouldn't
> need to send a new version only due to that.
You missed Intel Wired LAN (intel-wired-lan@lists.osuosl.org) on this,
though the other versions did have it. Could you fix this up and be sure
to include Intel Wired LAN?
Thanks,
Tony
>> ---
>> v2
>> - Update the size calculation with IFNAMSIZ and sizeof(i40e_dbg_command_buf)
>> v3
>> - Use kasprintf to improve readability and maintainability
>> v4
>> - Fix memory leak in error path
next prev parent reply other threads:[~2023-12-07 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 9:58 [PATCH v4 iwl-next] i40e: Use correct buffer size in i40e_dbg_command_read Kunwu Chan
2023-12-06 12:40 ` Alexander Lobakin
2023-12-07 23:25 ` Tony Nguyen [this message]
2023-12-08 2:05 ` Kunwu Chan
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=92e5cc01-e8b3-b6d2-e884-3d6bd001f0d0@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=chentao@kylinos.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=kunwu.chan@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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