All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: torvalds@linux-foundation.org
Cc: chandanbabu@kernel.org,djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: new code for 6.7
Date: Sat, 25 Nov 2023 18:17:49 +0530	[thread overview]
Message-ID: <87fs0um1rw.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)

Hi Linus,

Please pull this branch with changes for xfs for 6.7-rc3. XFS now validates
quota records recovered from the log before writing them to the disk.

I did a test-merge with the main upstream branch as of a few minutes ago and
didn't see any conflicts.  Please let me know if you encounter any problems.

The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:

  Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.7-fixes-3

for you to fetch changes up to 9c235dfc3d3f901fe22acb20f2ab37ff39f2ce02:

  xfs: dquot recovery does not validate the recovered dquot (2023-11-22 23:39:36 +0530)

----------------------------------------------------------------
Code changes for 6.7-rc2:

 * Validate quota records recovered from the log before writing them to the
   disk.

Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>

----------------------------------------------------------------
Darrick J. Wong (2):
      xfs: clean up dqblk extraction
      xfs: dquot recovery does not validate the recovered dquot

 fs/xfs/xfs_dquot.c              |  5 +++--
 fs/xfs/xfs_dquot_item_recover.c | 21 ++++++++++++++++++---
 2 files changed, 21 insertions(+), 5 deletions(-)

             reply	other threads:[~2023-11-25 12:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 12:47 Chandan Babu R [this message]
2023-11-25 17:13 ` [GIT PULL] xfs: new code for 6.7 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  9:56 Chandan Babu R
2023-11-08  9:56 ` Chandan Babu R
2023-11-08 21:29 ` Linus Torvalds
2023-11-08 22:52   ` Darrick J. Wong
2023-11-09  4:51     ` Christoph Hellwig
2023-11-09  7:39       ` Darrick J. Wong
2023-11-09 14:46         ` Christoph Hellwig
2023-11-09 16:38           ` Darrick J. Wong
2023-11-09 16:50             ` Christoph Hellwig
2023-11-09 22:05         ` Dave Chinner
2023-11-09 17:12   ` Jeff Layton
2023-11-08 21:34 ` 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=87fs0um1rw.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.