From: Roman Penyaev <rpenyaev@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Max Neunhoeffer <max@arangodb.com>,
Christopher Kohlhoff <chris.kohlhoff@clearpool.io>,
Davidlohr Bueso <dbueso@suse.de>, Jason Baron <jbaron@akamai.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] epoll: fix possible lost wakeup on epoll_ctl() path
Date: Mon, 10 Feb 2020 10:43:47 +0100 [thread overview]
Message-ID: <55c054e4c52c1e659cfa5f38a5e37571@suse.de> (raw)
In-Reply-To: <20200209215916.15640598689d3e40aa3f9e72@linux-foundation.org>
On 2020-02-10 06:59, Andrew Morton wrote:
> On Tue, 04 Feb 2020 18:20:03 +0100 Roman Penyaev <rpenyaev@suse.de>
> wrote:
>
>> On 2020-02-04 17:32, Jakub Kicinski wrote:
>> > On Tue, 04 Feb 2020 11:41:42 +0100, Roman Penyaev wrote:
>> >> Hi Andrew,
>> >>
>> >> Could you please suggest me, do I need to include Reported-by tag,
>> >> or reference to the bug is enough?
>> >
>> > Sorry to jump in but FWIW I like the Reported-and-bisected-by tag to
>> > fully credit the extra work done by the reporter.
>>
>> Reported-by: Max Neunhoeffer <max@arangodb.com>
>> Bisected-by: Max Neunhoeffer <max@arangodb.com>
>>
>> Correct?
>
> We could do that, but preferably with Max's approval (please?).
>
> Because people sometimes have issues with having their personal info
> added to the kernel commit record without having being asked.
Max approved. I've just resent v2, no code changes, comment
tweaks and 2 explicit tags with Max's name.
--
Roman
prev parent reply other threads:[~2020-02-10 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 20:59 Roman Penyaev
2020-02-03 20:59 ` [PATCH 2/3] epoll: ep->wq can be woken up unlocked in certain cases Roman Penyaev
2020-02-03 20:59 ` [PATCH 3/3] kselftest: introduce new epoll test case Roman Penyaev
2020-02-04 10:41 ` [PATCH 1/3] epoll: fix possible lost wakeup on epoll_ctl() path Roman Penyaev
2020-02-04 16:32 ` Jakub Kicinski
2020-02-04 17:20 ` Roman Penyaev
2020-02-04 22:29 ` Jakub Kicinski
2020-02-10 5:59 ` Andrew Morton
2020-02-10 6:44 ` Max Neunhöffer
2020-02-10 9:43 ` Roman Penyaev [this message]
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=55c054e4c52c1e659cfa5f38a5e37571@suse.de \
--to=rpenyaev@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chris.kohlhoff@clearpool.io \
--cc=dbueso@suse.de \
--cc=jbaron@akamai.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@arangodb.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
all inboxes | Powered by JetHome®