From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: 5.13 NFSD: completely broken?
Date: Wed, 30 Jun 2021 14:08:24 -0400 [thread overview]
Message-ID: <20210630180824.GF20229@fieldses.org> (raw)
In-Reply-To: <EEA82A83-433C-49C2-BD70-BBAE98961705@oracle.com>
On Wed, Jun 30, 2021 at 04:28:47PM +0000, Chuck Lever III wrote:
> The problem was discovered by static analysis, not a
> crash report. IMO the fix should have waited for testing
> and review by the NFS community. This close to a final
> release, the fixes for the array overrun and page leak
> could have gone into v5.13.1. I hope automation will
> take care of all of this very soon.
Years ago I had a cron job that fetched a few trees and ran cron jobs on
them nightly. "Automatic" testing always ends up requiring more manual
intervention than I expect, but maybe I should give that another
shot....
--b.
next prev parent reply other threads:[~2021-06-30 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 15:53 5.13 NFSD: completely broken? Russell King (Oracle)
2021-06-30 15:55 ` Chuck Lever III
2021-06-30 16:05 ` Bruce Fields
2021-06-30 16:28 ` Chuck Lever III
2021-06-30 18:08 ` Bruce Fields [this message]
2021-06-30 16:40 ` Russell King (Oracle)
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=20210630180824.GF20229@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@armlinux.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.