From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: mwilck@suse.com, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Chao Leng <lengchao@huawei.com>, Daniel Wagner <dwagner@suse.de>,
linux-nvme@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] nvme: rdma/tcp: fix list corruption with anatt timer
Date: Tue, 27 Apr 2021 18:25:21 +0200 [thread overview]
Message-ID: <20210427162521.GA26528@lst.de> (raw)
In-Reply-To: <0ff2dbc0-0182-f54d-b750-084feac53601@suse.de>
On Tue, Apr 27, 2021 at 11:33:04AM +0200, Hannes Reinecke wrote:
> As indicated in my previous mail, please change the description. We have
> since established a actual reason (duplicate calls to add_timer()), so
> please list it here.
So what happens if the offending add_timer is changed to mod_timer?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: mwilck@suse.com, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Chao Leng <lengchao@huawei.com>, Daniel Wagner <dwagner@suse.de>,
linux-nvme@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] nvme: rdma/tcp: fix list corruption with anatt timer
Date: Tue, 27 Apr 2021 18:25:21 +0200 [thread overview]
Message-ID: <20210427162521.GA26528@lst.de> (raw)
In-Reply-To: <0ff2dbc0-0182-f54d-b750-084feac53601@suse.de>
On Tue, Apr 27, 2021 at 11:33:04AM +0200, Hannes Reinecke wrote:
> As indicated in my previous mail, please change the description. We have
> since established a actual reason (duplicate calls to add_timer()), so
> please list it here.
So what happens if the offending add_timer is changed to mod_timer?
next prev parent reply other threads:[~2021-04-27 16:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 8:52 [PATCH v3] nvme: rdma/tcp: fix list corruption with anatt timer mwilck
2021-04-27 8:52 ` mwilck
2021-04-27 9:16 ` Daniel Wagner
2021-04-27 9:16 ` Daniel Wagner
2021-04-27 9:33 ` Hannes Reinecke
2021-04-27 9:33 ` Hannes Reinecke
2021-04-27 16:25 ` Christoph Hellwig [this message]
2021-04-27 16:25 ` Christoph Hellwig
2021-04-27 18:05 ` Hannes Reinecke
2021-04-27 18:05 ` Hannes Reinecke
2021-04-27 18:10 ` Christoph Hellwig
2021-04-27 18:10 ` Christoph Hellwig
2021-04-27 19:54 ` Martin Wilck
2021-04-27 19:54 ` Martin Wilck
2021-04-28 6:35 ` Hannes Reinecke
2021-04-28 6:35 ` Hannes Reinecke
2021-04-28 6:41 ` Martin Wilck
2021-04-28 6:41 ` Martin Wilck
2021-04-28 6:39 ` Maurizio Lombardi
2021-04-28 6:39 ` Maurizio Lombardi
2021-04-28 7:06 ` Martin Wilck
2021-04-28 7:06 ` Martin Wilck
2021-04-28 7:21 ` Maurizio Lombardi
2021-04-28 7:21 ` Maurizio Lombardi
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=20210427162521.GA26528@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mwilck@suse.com \
--cc=sagi@grimberg.me \
--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 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.