mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Arnaud Lecomte <contact@arnaud-lcm.com>
Cc: jfs-discussion@lists.sourceforge.net,
	syzbot+cffd18309153948f3c3e@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org, skhan@linuxfoundation.org
Subject: Re: [Jfs-discussion] [PATCH] jfs: upper bound check of tree index in dbAllocAG
Date: Mon, 28 Jul 2025 12:58:13 -0500	[thread overview]
Message-ID: <32e5a374-3b00-4450-a1f7-2729f1e3dfec@oracle.com> (raw)
In-Reply-To: <efd5366c-811b-482c-9e69-ce2fe1ef3295@arnaud-lcm.com>

On 7/27/25 4:55AM, Arnaud Lecomte wrote:
> Hi Dave,
> I am bumping the thread as I was wondering if you have some updates.
> Thanks !

It's in linux-next. I'll be pushing it to Linus this week.

Thanks,
Shaggy
> 
> On 14/07/2025 21:35, Lecomte, Arnaud wrote:
>> Thanks Dave !
>>
>> On 11/07/2025 20:23, Dave Kleikamp wrote:
>>> I'm finally trying to catch up.
>>>
>>> On 4/23/25 5:13PM, Arnaud Lecomte via Jfs-discussion wrote:
>>>> When computing the tree index in dbAllocAG, we never check we are not
>>>> out of bounds from the size of the stree.
>>>> This could happen in a scenario where the filesystem metadata are
>>>> corrupted.
>>>
>>> Looks good. I'll apply and test this.
>>>
>>>>
>>>> Reported-by: syzbot+cffd18309153948f3c3e@syzkaller.appspotmail.com
>>>> Closes: https://syzkaller.appspot.com/bug?extid=cffd18309153948f3c3e
>>>> Tested-by: syzbot+cffd18309153948f3c3e@syzkaller.appspotmail.com
>>>> Fixes: 263e55949d89 ("x86/cpu/amd: Fix workaround for erratum 1054")
>>>
>>> Removing the Fixes: line. This doesn't make sense.
>>>
>>>> Signed-off-by: Arnaud Lecomte <contact@arnaud-lcm.com>
>>>> ---
>>>>   fs/jfs/jfs_dmap.c | 6 ++++++
>>>>   1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
>>>> index 26e89d0c69b6..7acebb9a21b0 100644
>>>> --- a/fs/jfs/jfs_dmap.c
>>>> +++ b/fs/jfs/jfs_dmap.c
>>>> @@ -1385,6 +1385,12 @@ dbAllocAG(struct bmap * bmp, int agno, s64 
>>>> nblocks, int l2nb, s64 * results)
>>>>           (1 << (L2LPERCTL - (bmp->db_agheight << 1))) / bmp- 
>>>> >db_agwidth;
>>>>       ti = bmp->db_agstart + bmp->db_agwidth * (agno & (agperlev - 1));
>>>>   +    if (ti < 0 || ti >= le32_to_cpu(dcp->nleafs)) {
>>>> +        jfs_error(bmp->db_ipbmap->i_sb, "Corrupt dmapctl page: ti 
>>>> out of bounds\n");
>>>> +        release_metapage(mp);
>>>> +        return -EIO;
>>>> +    }
>>>> +
>>>>       /* dmap control page trees fan-out by 4 and a single allocation
>>>>        * group may be described by 1 or 2 subtrees within the ag level
>>>>        * dmap control page, depending upon the ag size. examine the 
>>>> ag's
>>>>
>>>> ---
>>>> base-commit: 8560697b23dc2f405cb463af2b17256a9888129d
>>>> change-id: 20250423-ubsan-jfs-3a58acae5e57
>>>>
>>>> Best regards,
>>>
>>>


  reply	other threads:[~2025-07-28 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 22:13 Arnaud Lecomte
2025-07-11 19:23 ` [Jfs-discussion] " Dave Kleikamp
2025-07-14 20:35   ` Lecomte, Arnaud
2025-07-27  9:55     ` Arnaud Lecomte
2025-07-28 17:58       ` Dave Kleikamp [this message]
2025-07-28 18:14   ` Arnaud Lecomte

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=32e5a374-3b00-4450-a1f7-2729f1e3dfec@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=contact@arnaud-lcm.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+cffd18309153948f3c3e@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

all inboxes | Powered by JetHome®