From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Trond Myklebust <trondmy@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4/5] NFSv4/pnfs: Fix a page lock leak in nfs_pageio_resend()
Date: Tue, 13 Aug 2019 17:55:24 +0000 [thread overview]
Message-ID: <20190813175525.9B10720679@mail.kernel.org> (raw)
In-Reply-To: <20190813142806.123268-4-trond.myklebust@hammerspace.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d600ad1f2bdb NFS41: pop some layoutget errors to application.
The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189, v4.4.189.
v5.2.8: Build OK!
v4.19.66: Failed to apply! Possible dependencies:
078b5fd92c49 ("NFS: Clean up list moves of struct nfs_page")
v4.14.138: Failed to apply! Possible dependencies:
078b5fd92c49 ("NFS: Clean up list moves of struct nfs_page")
v4.9.189: Failed to apply! Possible dependencies:
078b5fd92c49 ("NFS: Clean up list moves of struct nfs_page")
v4.4.189: Failed to apply! Possible dependencies:
078b5fd92c49 ("NFS: Clean up list moves of struct nfs_page")
6272dcc6beeb ("NFS: Simplify nfs_request_add_commit_list() arguments")
b20135d0b243 ("NFSv4.1/pNFS: Don't queue up a new commit if the layout segment is invalid")
c18b96a1b862 ("nfs: clean up rest of reqs when failing to add one")
f57dcf4c7211 ("NFS: Fix I/O request leakages")
fe238e601d25 ("NFS: Save struct inode COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS Makefile README REPORTING-BUGS arch block certs crypto drivers firmware fs include init ipc kernel lib mm net samples scripts security sound tools usr virt inside nfs_commit_info to clarify usage of i_lock")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-13 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 14:28 [PATCH 1/5] NFS: Don't refresh attributes with mounted-on-file information Trond Myklebust
2019-08-13 14:28 ` [PATCH 2/5] NFSv4: Fix return values for nfs4_file_open() Trond Myklebust
2019-08-13 14:28 ` [PATCH 3/5] NFSv4: Fix return value in nfs_finish_open() Trond Myklebust
2019-08-13 14:28 ` [PATCH 4/5] NFSv4/pnfs: Fix a page lock leak in nfs_pageio_resend() Trond Myklebust
2019-08-13 14:28 ` [PATCH 5/5] NFS: Ensure O_DIRECT reports an error if the bytes read/written is 0 Trond Myklebust
2019-08-13 17:55 ` Sasha Levin [this message]
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=20190813175525.9B10720679@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).