From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
"J. Bruce Fields" <bfields@redhat.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] reconnect_one(): fix a missing error code
Date: Fri, 16 Jun 2017 13:50:35 +0000 [thread overview]
Message-ID: <20170616135035.GB12030@fieldses.org> (raw)
In-Reply-To: <87injw7unk.fsf@notabene.neil.brown.name>
On Fri, Jun 16, 2017 at 08:28:31AM +1000, NeilBrown wrote:
> It wouldn't be too hard to create that scenario. It might be harder to
> find a way to expose the corruption.
Yes. Well, in any case, I assume this Al's to take. ACK to the patch,
and it should go to stable as well.
--b.
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
"J. Bruce Fields" <bfields@redhat.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] reconnect_one(): fix a missing error code
Date: Fri, 16 Jun 2017 09:50:35 -0400 [thread overview]
Message-ID: <20170616135035.GB12030@fieldses.org> (raw)
In-Reply-To: <87injw7unk.fsf@notabene.neil.brown.name>
On Fri, Jun 16, 2017 at 08:28:31AM +1000, NeilBrown wrote:
> It wouldn't be too hard to create that scenario. It might be harder to
> find a way to expose the corruption.
Yes. Well, in any case, I assume this Al's to take. ACK to the patch,
and it should go to stable as well.
--b.
next prev parent reply other threads:[~2017-06-16 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 9:30 [PATCH] reconnect_one(): fix a missing error code Dan Carpenter
2017-06-14 9:30 ` Dan Carpenter
2017-06-14 20:34 ` J. Bruce Fields
2017-06-14 20:34 ` J. Bruce Fields
2017-06-14 21:54 ` NeilBrown
2017-06-14 21:54 ` NeilBrown
2017-06-15 9:26 ` Dan Carpenter
2017-06-15 9:26 ` Dan Carpenter
2017-06-15 21:40 ` J. Bruce Fields
2017-06-15 21:40 ` J. Bruce Fields
2017-06-15 22:28 ` NeilBrown
2017-06-15 22:28 ` NeilBrown
2017-06-16 13:50 ` J. Bruce Fields [this message]
2017-06-16 13:50 ` J. Bruce Fields
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=20170616135035.GB12030@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=neilb@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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.