mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.7
Date: Wed, 1 Nov 2023 08:22:09 -0500	[thread overview]
Message-ID: <425ffc38-a35b-45c4-9819-e51464f58450@oracle.com> (raw)

The following changes since commit 5e62ed3b1c8a397185af53d6b94f04b9ff21ec7d:

   Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2023-10-03 10:15:10 -0700)

are available in the Git repository at:

   git@github.com:kleikamp/linux-shaggy.git tags/jfs-6.7

for you to fetch changes up to a779ed754e52d582b8c0e17959df063108bd0656:

   jfs: define xtree root and page independently (2023-10-13 10:39:25 -0500)

----------------------------------------------------------------
Minor stability improvements

----------------------------------------------------------------
Dave Kleikamp (1):
       jfs: define xtree root and page independently

Juntong Deng (2):
       fs/jfs: Add check for negative db_l2nbperpage
       fs/jfs: Add validity check for db_maxag and db_agpref

Manas Ghandat (2):
       jfs: fix array-index-out-of-bounds in dbFindLeaf
       jfs: fix array-index-out-of-bounds in diAlloc

  fs/jfs/jfs_dinode.h |  2 +-
  fs/jfs/jfs_dmap.c   | 23 ++++++++++++++++++-----
  fs/jfs/jfs_imap.c   | 11 +++++++----
  fs/jfs/jfs_incore.h |  2 +-
  fs/jfs/jfs_txnmgr.c |  4 ++--
  fs/jfs/jfs_xtree.c  |  4 ++--
  fs/jfs/jfs_xtree.h  | 37 +++++++++++++++++++++++--------------
  7 files changed, 54 insertions(+), 29 deletions(-)

             reply	other threads:[~2023-11-01 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 13:22 Dave Kleikamp [this message]
2023-11-02 18:38 ` 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=425ffc38-a35b-45c4-9819-e51464f58450@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®