[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA4K+2aGYuRZW6prUi53vcEYhuCf4WvGEj384E-Ut-OJEm6wkA@mail.gmail.com>
Date: Mon, 7 Oct 2024 12:47:54 -0700
From: Kuntal Nayak <kuntal.nayak@...adcom.com>
To: Greg KH <gregkh@...uxfoundation.org>, linux-xfs@...r.kernel.org
Cc: leah.rumancik@...il.com, linux-kernel@...r.kernel.org,
ajay.kaher@...adcom.com, alexey.makhalov@...adcom.com,
vasavi.sirnapalli@...adcom.com, lei lu <llfamsec@...il.com>,
Dave Chinner <dchinner@...hat.com>, "Darrick J . Wong" <djwong@...nel.org>,
Chandan Babu R <chandanbabu@...nel.org>
Subject: Re: [PATCH v5.10] xfs: add bounds checking to xlog_recover_process_data
Thank you, Greg, for getting back to me. Following is the order for patches,
1. xfs: No need for inode number error injection in __xfs_dir3_data_check
2. xfs: don't walk off the end of a directory data block
3. xfs: add bounds checking to xlog_recover_process_data
Hello xfs-team, could you kindly assist me in reviewing the 3 patches
listed above for LTS v5.10?
------
Sincerely,
Kuntal
On Fri, Sep 27, 2024 at 1:00 AM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Tue, Sep 24, 2024 at 03:39:56PM -0700, Kuntal Nayak wrote:
> > From: lei lu <llfamsec@...il.com>
> >
> > [ Upstream commit fb63435b7c7dc112b1ae1baea5486e0a6e27b196 ]
>
> Also, what is the ordering here? Should I just guess?
Powered by blists - more mailing lists