From: Gaurav Kohli <gkohli@codeaurora.org>
To: Denis Efremov <efremov@linux.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
stable@vger.kernel.org, Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH v1] trace: Fix race in trace_open and buffer resize call
Date: Sat, 23 Jan 2021 22:03:27 +0530 [thread overview]
Message-ID: <46d1f82b-1eb4-a828-c79c-e6556eccf9d5@codeaurora.org> (raw)
In-Reply-To: <5959315a-507a-00df-031a-e60d45c1f7ab@linux.com>
On 1/23/2021 4:19 PM, Denis Efremov wrote:
>
>
> On 1/22/21 5:37 PM, Steven Rostedt wrote:
>> On Fri, 22 Jan 2021 16:55:29 +0530
>> Gaurav Kohli <gkohli@codeaurora.org> wrote:
>>
>>>>> That could possibly work.
>>>
>>> Yes, this will work, As i have tested similar patch for internal testing
>>> for kernel branches like 5.4/4.19.
>>
>> Can you or Denis send a proper patch for Greg to backport? I'll review it,
>> test it and give my ack to it, so Greg can take it without issue.
>>
>
> I can prepare the patch, but it will be compile-tested only from my side. Honestly,
> I think it's better when the patch and its backports have the same author and
> commit message. And I can't test the fix by myself as I don't know how to reproduce
> conditions for the bug. I think it's better if Gaurav will prepare this backport,
> unless he have reasons for me to do it or maybe just don't have enough time nowadays.
> Gaurav, if you want to somehow mention me you add my Reported-by:
>
> Thanks,
> Denis
>
Sure I will do, I have never posted on backport branches. Let me check
and post it.
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2021-01-23 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 9:33 [PATCH v1] trace: Fix race in trace_open and buffer resize call Gaurav Kohli
2021-01-21 14:30 ` Denis Efremov
2021-01-21 19:09 ` Steven Rostedt
2021-01-21 20:15 ` Denis Efremov
2021-01-21 20:37 ` Steven Rostedt
2021-01-22 10:59 ` Greg KH
2021-01-22 11:25 ` Gaurav Kohli
2021-01-22 14:37 ` Steven Rostedt
2021-01-23 10:49 ` Denis Efremov
2021-01-23 16:33 ` Gaurav Kohli [this message]
2021-01-24 3:21 ` Steven Rostedt
2021-01-24 9:57 ` Gaurav Kohli
2021-01-24 10:05 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-09-24 13:55 Gaurav Kohli
2020-10-05 4:39 ` Gaurav Kohli
2020-10-05 14:25 ` Steven Rostedt
2020-10-05 14:27 ` Steven Rostedt
2020-10-05 16:29 ` Gaurav Kohli
2020-10-05 16:32 ` Steven Rostedt
2020-10-05 17:38 ` Gaurav Kohli
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=46d1f82b-1eb4-a828-c79c-e6556eccf9d5@codeaurora.org \
--to=gkohli@codeaurora.org \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).