From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "bcodding\@redhat.com" <bcodding@redhat.com>,
"Anna.Schumaker\@netapp.com" <Anna.Schumaker@netapp.com>,
"linux-nfs\@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Chuck.Lever\@oracle.com" <Chuck.Lever@oracle.com>
Subject: Re: Need help debugging NFS issues new to 4.20 kernel
Date: Tue, 19 Feb 2019 20:13:14 -0600 [thread overview]
Message-ID: <ufa4l8z5hs5.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <e8887651e91b1d0110cab2330a03e3e3ccef742b.camel@hammerspace.com> (Trond Myklebust's message of "Sat, 16 Feb 2019 14:46:45 +0000")
>>>>> "TM" == Trond Myklebust <trondmy@hammerspace.com> writes:
TM> Hmm... Does the following patch help at all?
I un-wrapped it and applied it over 4.20.10 and pushed it out to a
couple of problematic machines. So far it's been OK there, so I've
rolled it out to 50 desktops (because they happen to have secure boot
disabled and thus allow me to boot custom kernels) and I guess we'll see
how that goes.
- J<
next prev parent reply other threads:[~2019-02-20 2:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 17:32 Need help debugging NFS issues new to 4.20 kernel Jason L Tibbitts III
2019-01-24 19:28 ` Jason L Tibbitts III
2019-01-24 19:58 ` Trond Myklebust
2019-01-25 19:13 ` Schumaker, Anna
2019-01-26 17:59 ` Sasha Levin
2019-01-25 19:51 ` Jason L Tibbitts III
2019-02-05 18:12 ` Jason Tibbitts
2019-02-06 12:05 ` Benjamin Coddington
[not found] ` <87imxwab12.fsf@hippogriff.math.uh.edu>
2019-02-07 11:13 ` Benjamin Coddington
[not found] ` <87d0o3aadg.fsf@hippogriff.math.uh.edu>
2019-02-08 12:01 ` Benjamin Coddington
2019-02-08 15:19 ` Chuck Lever
2019-02-08 17:17 ` Jason L Tibbitts III
2019-02-15 20:33 ` Jason L Tibbitts III
2019-02-16 14:46 ` Trond Myklebust
2019-02-20 2:13 ` Jason L Tibbitts III [this message]
2019-02-20 15:25 ` Jason L Tibbitts III
2019-02-20 15:37 ` Trond Myklebust
2019-02-20 15:39 ` Chuck Lever
2019-02-20 15:41 ` Trond Myklebust
2019-02-21 18:19 ` Jason L Tibbitts III
2019-02-25 19:24 ` Jason L Tibbitts III
2019-02-25 23:15 ` Benjamin Coddington
2019-02-20 16:25 ` Jason L Tibbitts III
2019-02-20 16:45 ` Trond Myklebust
2019-02-20 16:49 ` Jason L Tibbitts III
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=ufa4l8z5hs5.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=Anna.Schumaker@netapp.com \
--cc=Chuck.Lever@oracle.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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 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.