From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, jlayton@kernel.org,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL]
Date: Tue, 09 Aug 2022 14:27:25 +0100 [thread overview]
Message-ID: <431242.1660051645@warthog.procyon.org.uk> (raw)
Hi Linus,
Can you pull these two patches please? The first fixes a cookie access ref
leak if a cookie is invalidated a second time before the first invalidation
is actually processed. The second adds a tracepoint to log cookie look up
failure.
Thanks,
David
Link: https://listman.redhat.com/archives/linux-cachefs/2022-August/007061.html
Link: https://listman.redhat.com/archives/linux-cachefs/2022-August/007062.html
---
The following changes since commit 3d7cb6b04c3f3115719235cc6866b10326de34cd:
Linux 5.19 (2022-07-31 14:03:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-fixes-20220809
for you to fetch changes up to 1a1e3aca9d4957e282945cdc2b58e7c560b8e0d2:
fscache: add tracepoint when failing cookie (2022-08-09 14:13:59 +0100)
----------------------------------------------------------------
fscache fixes
----------------------------------------------------------------
Jeff Layton (2):
fscache: don't leak cookie access refs if invalidation is in progress or failed
fscache: add tracepoint when failing cookie
fs/fscache/cookie.c | 9 +++++++--
include/trace/events/fscache.h | 2 ++
2 files changed, 9 insertions(+), 2 deletions(-)
next reply other threads:[~2022-08-09 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:27 David Howells [this message]
2022-08-09 13:58 ` [GIT PULL] fscache: Invalidation fix and new tracepoint David Howells
2022-08-09 17:29 ` [GIT PULL] pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-06-03 19:20 Eric W. Biederman
2022-06-03 23:25 ` pr-tracker-bot
2021-12-23 19:55 Eric W. Biederman
2018-05-08 13:38 Frederic Weisbecker
2016-04-12 18:34 David Howells
2012-03-13 4:56 [git pull] Jesse Barnes
2011-02-11 13:40 [GIT PULL] Ted Ts'o
2011-02-12 0:33 ` Linus Torvalds
2011-02-12 1:41 ` Eric Sandeen
2011-02-12 13:28 ` Ted Ts'o
2010-09-10 12:52 Nicolas Ferre
2010-09-10 13:16 ` Jean-Christophe PLAGNIOL-VILLARD
2010-03-03 3:09 Frederic Weisbecker
2007-10-23 9:43 Haavard Skinnemoen
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=431242.1660051645@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome