From: Greg KH <greg@kroah.com>
To: joeyli <jlee@suse.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
linux-block@vger.kernel.org,
Chun-Yi Lee <joeyli.kernel@gmail.com>,
stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jens Axboe <axboe@kernel.dk>, Justin Sanders <justin@coraid.com>,
Kirill Korotaev <dev@openvz.org>,
Nicolai Stange <nstange@suse.com>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [PATCH v2] aoe: fix the potential use-after-free problem in more places
Date: Mon, 24 Jun 2024 14:45:38 +0200 [thread overview]
Message-ID: <2024062433-maximum-purplish-4ccc@gregkh> (raw)
In-Reply-To: <20240624115445.GL7611@linux-l9pv.suse>
On Mon, Jun 24, 2024 at 07:54:45PM +0800, joeyli wrote:
> On Mon, Jun 24, 2024 at 01:43:25PM +0200, Markus Elfring wrote:
> > >>> … So they should also use dev_hold() to increase the
> > >>> refcnt of skb->dev.
> > >> …
> > >>
> > >> reference counter of “skb->dev”?
> > >
> > > Yes, I will update my wording.
> >
> > Would you like to improve such a change description also with imperative wordings?
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc4#n94
> >
> >
> > How do you think about the text “Prevent use-after-free issues at more places”
> > for a summary phrase?
> >
>
> Thanks for your suggestion. I will update the wording in next version.
Hi,
This is the semi-friendly patch-bot of Greg Kroah-Hartman.
Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list. I strongly suggest that you not do this anymore. Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.
Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all. The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback. Please feel free to also ignore emails
from them.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2024-06-24 12:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 6:44 [PATCH v2] aoe: fix the potential use-after-free problem in more places Chun-Yi Lee
2024-06-24 7:05 ` Greg KH
2024-06-24 11:00 ` joeyli
2024-06-24 8:40 ` Markus Elfring
2024-06-24 11:01 ` joeyli
2024-06-24 11:43 ` Markus Elfring
2024-06-24 11:54 ` joeyli
2024-06-24 12:45 ` Greg KH [this message]
2024-06-24 9:27 ` Markus Elfring
2024-06-24 11:04 ` joeyli
2024-06-24 11:28 ` Markus Elfring
2024-06-24 11:45 ` joeyli
2024-06-25 10:48 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 10:29 Chun-Yi Lee
2024-09-12 10:58 ` Valentin Kleibel
2024-09-16 9:23 ` joeyli
2024-10-02 5:53 ` joeyli
2024-11-04 13:38 ` Valentin Kleibel
2024-11-11 13:53 ` joeyli
2024-09-12 11:01 ` Greg KH
2024-06-13 4:15 Chun-Yi Lee
2024-05-14 15:18 Chun-Yi Lee
2024-05-14 15:34 ` Markus Elfring
2024-05-15 5:09 ` joeyli
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=2024062433-maximum-purplish-4ccc@gregkh \
--to=greg@kroah.com \
--cc=Markus.Elfring@web.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=justin@coraid.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nstange@suse.com \
--cc=stable@vger.kernel.org \
--cc=xemul@openvz.org \
/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.