From: Greg KH <gregkh@linuxfoundation.org>
To: Xia Fukun <xiafukun@huawei.com>
Cc: prajnoha@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] kobject: Fix global-out-of-bounds in kobject_action_type()
Date: Wed, 14 Jun 2023 22:09:06 +0200 [thread overview]
Message-ID: <2023061444-latticed-discuss-fa70@gregkh> (raw)
In-Reply-To: <86c6040d-17ab-fb01-2b75-717d82ba9345@huawei.com>
On Wed, Jun 14, 2023 at 07:32:38PM +0800, Xia Fukun wrote:
>
> On 2023/5/18 17:16, Xia Fukun wrote:
> > ---
> > v6 -> v7:
> > - Move macro UEVENT_KACT_STRSIZE to the .c file to
> > improve maintainability.
> >
>
> Gentle ping ...
>
> UEVENT_KACT_STRSIZE is defined as the maximum length of the string
> contained in kobject_actions[].
>
> At present, the maximum length of strings in this array is 7. Based on
> the actual meaning of these strings, these actions will not exceed 16
> if there are any subsequent changes.
>
> I have submitted v7 of the patch according to your suggestion and
> tested it to ensure its functionality is correct.
It's in my to-review queue, but I was hoping that others would at least
test it out given that the previous versions had so many problems. I am
loath to do that on my own, sorry.
> Please take the time to review it.
How did you test it? How have you verified that the previous failures
were caught this time?
You can understand my hesitancy here, right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-14 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 9:16 [PATCH v7] kobject: Fix global-out-of-bounds in kobject_action_type() Xia Fukun
2023-06-14 11:32 ` Xia Fukun
2023-06-14 20:09 ` Greg KH [this message]
2023-06-15 1:43 ` Xia Fukun
2023-06-15 6:04 ` Greg KH
2023-10-05 11:48 ` Greg KH
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=2023061444-latticed-discuss-fa70@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prajnoha@redhat.com \
--cc=xiafukun@huawei.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