mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	Chris Tracy <ctracy@engr.scu.edu>,
	linux-nfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	it+linux-nfs@molgen.mpg.de
Subject: Re: [PATCH] nfsd: Fix overflow causing non-working mounts on 1 TB machines
Date: Wed, 3 Jul 2019 18:03:06 +0200	[thread overview]
Message-ID: <267fb3de-fe3b-fb42-1cc1-3faea5d19d93@molgen.mpg.de> (raw)
In-Reply-To: <20190703155634.GB23076@parsley.fieldses.org>

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

Dear Bruce,


On 7/3/19 5:56 PM, J. Bruce Fields wrote:
> Good catch!  And thanks for the detailed explanation.  Applying for 5.2
> and stable.

Thanks. Please note, that in the last part are some guesses, and I am not
well versed in the terminology. So please feel free to reword the commit
messages.


Kind regards,

Paul


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2019-07-03 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190702165107.93C8A2067CFDD@mx.molgen.mpg.de>
     [not found] ` <8c3e0249-b17f-4bd2-4a46-afd4d35f4763@molgen.mpg.de>
2019-07-02 21:59   ` Regression caused by commit c54f24e3 (nfsd: fix performance-limiting session calculation) Paul Menzel
2019-07-03  9:56     ` Paul Menzel
2019-07-03 12:54       ` [PATCH] nfsd: Fix overflow causing non-working mounts on 1 TB machines Paul Menzel
2019-07-03 15:56         ` J. Bruce Fields
2019-07-03 16:03           ` Paul Menzel [this message]
2019-07-03 16:43             ` 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=267fb3de-fe3b-fb42-1cc1-3faea5d19d93@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=bfields@redhat.com \
    --cc=ctracy@engr.scu.edu \
    --cc=it+linux-nfs@molgen.mpg.de \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®