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 v6.6
Date: Thu, 31 Aug 2023 10:21:26 -0500 [thread overview]
Message-ID: <e73dbacc-f2ba-4210-879e-42524a4d6283@oracle.com> (raw)
The following changes since commit 74f1456c4a5f3d7da4102ecae5c20370f89c6ed1:
Merge tag 'linux-kselftest-fixes-6.5-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest (2023-07-18 08:56:02 -0700)
are available in the Git repository at:
git@github.com:kleikamp/linux-shaggy.git tags/jfs-6.6
for you to fetch changes up to 0225e10972fa809728b8d4c1bd2772b3ec3fdb57:
jfs: validate max amount of blocks before allocation. (2023-08-29 12:25:47 -0500)
----------------------------------------------------------------
A few small fixes
----------------------------------------------------------------
Alexei Filippov (1):
jfs: validate max amount of blocks before allocation.
Andrew Kanner (1):
fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount()
Colin Ian King (1):
jfs: remove redundant initialization to pointer ip
Immad Mir (1):
FS: JFS: (trivial) Fix grammatical error in extAlloc
Liu Shixin via Jfs-discussion (1):
jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount
fs/jfs/jfs_dmap.c | 1 +
fs/jfs/jfs_extent.c | 7 ++++++-
fs/jfs/jfs_imap.c | 1 +
fs/jfs/namei.c | 2 +-
4 files changed, 9 insertions(+), 2 deletions(-)
next reply other threads:[~2023-08-31 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 15:21 Dave Kleikamp [this message]
2023-08-31 22:42 ` 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=e73dbacc-f2ba-4210-879e-42524a4d6283@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®