From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: sangsup lee <k1rh4.lee@gmail.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] misc: fastrpc: Fix a Use after-free-bug by race condition
Date: Thu, 27 Apr 2023 14:27:06 +0200 [thread overview]
Message-ID: <2023042722-humble-unthread-9597@gregkh> (raw)
In-Reply-To: <CAJkuJRhqU++S+xYPDFDyxawfz_ePGJ0oTk-ZZg8N8BSfKcSdDA@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Apr 27, 2023 at 08:51:48PM +0900, sangsup lee wrote:
> I reported fastrpc bug in
> Feb,2023.(https://lore.kernel.org/lkml/20230216014120.3110-1-k1rh4.lee@gmail.com)
That was a patch, not a bug report. How was this tested?
> And Srinivas recommended this patch code for patch v2.
> That's why I sent this patch v2 however, I haven't received any reply
> after that.
>
> I just want to know the next step for patching this code.
> Should I just keep waiting ? Or Please let me know if I need to
> provide you with more information.
Please read my comments on my last email on the patch for what you need
to address.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-27 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 1:36 [PATCH v2] misc: fastrpc: Fix a Use after-free-bug by race condition Sangsup Lee
2023-04-27 9:29 ` sangsup lee
2023-04-27 9:52 ` Greg Kroah-Hartman
2023-04-27 11:51 ` sangsup lee
2023-04-27 12:27 ` Greg Kroah-Hartman [this message]
2023-04-28 5:00 ` sangsup lee
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=2023042722-humble-unthread-9597@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=k1rh4.lee@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox