From: Christoph Hellwig <hch@lst.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Brian Foster <bfoster@redhat.com>, Christoph Hellwig <hch@lst.de>,
it+linux-nfs@molgen.mpg.de, linux-nfs@vger.kernel.org,
linux-xfs@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>
Subject: Re: Locking problems with Linux 4.9 and 4.11 with NFSD and `fs/iomap.c`
Date: Wed, 28 Jun 2017 18:41:37 +0200 [thread overview]
Message-ID: <20170628164137.GA8248@lst.de> (raw)
In-Reply-To: <f6115b81-918d-ecfe-e3d9-812bccf7c80f@molgen.mpg.de>
On Tue, Jun 27, 2017 at 01:59:46PM +0200, Paul Menzel wrote:
> Dear Brian, dear Christoph,
>
>
> Just a small update that we were hit by the problem on a different machine
> (identical model) with Linux 4.9.32 and the exact same symptoms.
Thanks for the update. I have to admit this issue completely dropped
off my table, but I'll try to get back to it in the next days.
next prev parent reply other threads:[~2017-06-28 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 19:09 Locking problems with Linux 4.9 with NFSD and `fs/iomap.c` Paul Menzel
2017-05-08 13:18 ` Brian Foster
2017-05-09 9:05 ` Christoph Hellwig
[not found] ` <7ae18b0d-38e3-9b12-0989-ede68956ad43@molgen.mpg.de>
[not found] ` <358037e8-6784-ebca-9fbb-ec7eef3977d6@molgen.mpg.de>
[not found] ` <20170510171757.GA10534@localhost.localdomain>
2017-06-27 11:59 ` Locking problems with Linux 4.9 and 4.11 " Paul Menzel
2017-06-28 16:41 ` Christoph Hellwig [this message]
2017-08-01 17:49 ` Paul Menzel
2017-08-01 22:51 ` Dave Chinner
2017-08-10 14:11 ` Paul Menzel
2017-08-10 14:11 ` Paul Menzel
2017-08-10 19:54 ` AW: " Markus Stockhausen
2017-08-10 19:54 ` Markus Stockhausen
2017-08-11 10:15 ` Christoph Hellwig
2017-08-11 15:14 ` Paul Menzel
2017-05-10 9:08 ` Locking problems with Linux 4.9 " Paul Menzel
2017-05-10 17:23 ` 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=20170628164137.GA8248@lst.de \
--to=hch@lst.de \
--cc=bfields@fieldses.org \
--cc=bfoster@redhat.com \
--cc=it+linux-nfs@molgen.mpg.de \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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.