From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"jfs-discussion@lists.sourceforge.net"
<jfs-discussion@lists.sourceforge.net>
Subject: [GIT PULL] jfs updates for 6.17
Date: Thu, 31 Jul 2025 09:06:11 -0500 [thread overview]
Message-ID: <1ab1a9e3-037d-473f-954d-248037f2ec03@oracle.com> (raw)
The following changes since commit bc9ff192a6c940d9a26e21a0a82f2667067aaf5f:
Merge tag 'net-6.16-rc6' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2025-07-10
09:18:53 -0700)
are available in the Git repository at:
git@github.com:kleikamp/linux-shaggy.git tags/jfs-6.17
for you to fetch changes up to 856db37592021e9155384094e331e2d4589f28b1:
jfs: fix metapage reference count leak in dbAllocCtl (2025-07-29
08:34:57 -0500)
----------------------------------------------------------------
Fixes and cleanups for JFS filesystem
----------------------------------------------------------------
Arnaud Lecomte (1):
jfs: upper bound check of tree index in dbAllocAG
Christoph Hellwig (1):
jfs: stop using write_cache_pages
Edward Adam Davis (1):
jfs: Regular file corruption check
Lizhi Xu (1):
jfs: truncate good inode pages when hard link is 0
Suchit Karunakaran (1):
jfs: jfs_xtree: replace XT_GETPAGE macro with xt_getpage()
Zheng Yu (1):
jfs: fix metapage reference count leak in dbAllocCtl
fs/jfs/file.c | 3 ++
fs/jfs/inode.c | 2 +-
fs/jfs/jfs_dmap.c | 10 +++-
fs/jfs/jfs_metapage.c | 8 +--
fs/jfs/jfs_xtree.c | 142
+++++++++++++++++++++++++++-----------------------
5 files changed, 96 insertions(+), 69 deletions(-)
next reply other threads:[~2025-07-31 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:06 Dave Kleikamp [this message]
2025-07-31 17:56 ` pr-tracker-bot
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=1ab1a9e3-037d-473f-954d-248037f2ec03@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®