From: Greg KH <gregkh@linuxfoundation.org>
To: "Sergio González Collado" <sergio.collado@gmail.com>
Cc: stable@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Dave Kleikamp <dave.kleikamp@oracle.com>,
Manas Ghandat <ghandatmanas@gmail.com>,
syzbot+6b1d79dad6cc6b3eef41@syzkaller.appspotmail.com
Subject: Re: [PATCH 6.1.y] jfs: define xtree root and page independently
Date: Mon, 12 Aug 2024 16:37:55 +0200 [thread overview]
Message-ID: <2024081227-habitat-cough-dfb0@gregkh> (raw)
In-Reply-To: <20240730201315.19917-1-sergio.collado@gmail.com>
On Tue, Jul 30, 2024 at 10:13:15PM +0200, Sergio González Collado wrote:
> From: Dave Kleikamp <dave.kleikamp@oracle.com>
>
> [ Upstream commit a779ed754e52d582b8c0e17959df063108bd0656 ]
>
> In order to make array bounds checking sane, provide a separate
> definition of the in-inode xtree root and the external xtree page.
>
> Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
> Tested-by: Manas Ghandat <ghandatmanas@gmail.com>
> (cherry picked from commit a779ed754e52d582b8c0e17959df063108bd0656)
> Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
> Reported-by: syzbot+6b1d79dad6cc6b3eef41@syzkaller.appspotmail.com
> ---
What about 6.6.y? We can't take commits only to older kernels, that
would mean you would have a regression.
Please resubmit for all relevant branches.
greg k-h
next prev parent reply other threads:[~2024-08-12 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 20:13 [PATCH 6.1.y] jfs: define xtree root and page independently Sergio González Collado
2024-08-12 14:37 ` Greg KH [this message]
2024-08-12 20:53 ` Sergio González Collado
2024-08-15 19:31 ` Sergio González Collado
-- strict thread matches above, loose matches on Subject: below --
2025-04-27 15:30 Aditya Dutt
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=2024081227-habitat-cough-dfb0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dave.kleikamp@oracle.com \
--cc=ghandatmanas@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=sergio.collado@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+6b1d79dad6cc6b3eef41@syzkaller.appspotmail.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