public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kuntal Nayak <kuntal.nayak@broadcom.com>
Cc: leah.rumancik@gmail.com, linux-xfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, ajay.kaher@broadcom.com,
	alexey.makhalov@broadcom.com, vasavi.sirnapalli@broadcom.com,
	lei lu <llfamsec@gmail.com>, Dave Chinner <dchinner@redhat.com>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Chandan Babu R <chandanbabu@kernel.org>
Subject: Re: [PATCH v5.10] xfs: add bounds checking to xlog_recover_process_data
Date: Fri, 27 Sep 2024 08:52:37 +0200	[thread overview]
Message-ID: <2024092725-chamber-compel-10b5@gregkh> (raw)
In-Reply-To: <20240924223958.347475-1-kuntal.nayak@broadcom.com>

On Tue, Sep 24, 2024 at 03:39:56PM -0700, Kuntal Nayak wrote:
> From: lei lu <llfamsec@gmail.com>
> 
> [ Upstream commit fb63435b7c7dc112b1ae1baea5486e0a6e27b196 ]

Also, what is the ordering here?  Should I just guess?

  parent reply	other threads:[~2024-09-27  8:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 22:39 [PATCH v5.10] xfs: add bounds checking to xlog_recover_process_data Kuntal Nayak
2024-09-24 22:39 ` [PATCH v5.10] xfs: No need for inode number error injection in __xfs_dir3_data_check Kuntal Nayak
2024-09-24 22:39 ` [PATCH v5.10] xfs: don't walk off the end of a directory data block Kuntal Nayak
2024-09-27  6:52 ` [PATCH v5.10] xfs: add bounds checking to xlog_recover_process_data Greg KH
2024-09-27  6:52 ` Greg KH [this message]
2024-10-07 19:47   ` Kuntal Nayak
2024-10-07 20:53     ` Leah Rumancik

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=2024092725-chamber-compel-10b5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=chandanbabu@kernel.org \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=kuntal.nayak@broadcom.com \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=llfamsec@gmail.com \
    --cc=vasavi.sirnapalli@broadcom.com \
    /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