From: Ulrich Hecht <uli@fpond.eu>
To: pavel@nabladev.com
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: [cip-dev] Request for review for 4.4-st78, 4.4-cip113
Date: Tue, 14 Jul 2026 22:47:26 +0200 (CEST) [thread overview]
Message-ID: <1138844765.324155.1784062046046@webmail.strato.de> (raw)
In-Reply-To: <alS_410BkUAadIMY@duo.ucw.cz>
Hi!
Thanks for the reviews.
> On 07/13/2026 12:37 PM CEST Pavel Machek via lists.cip-project.org <pavel=nabladev.com@lists.cip-project.org> wrote:
> For now, I have not checked the batman-adv stuff. Two comments below.
[...]
> ! no dec in munmap? , c/e, will we now have framebuffer refusing resize? > 0bd353e476ab2 fbdev: udlfb: add vm_ops to dlfb_ops_mmap to prevent use-after-free
>
> I don't see how this works. mmap_count is increased in mmap, but I
> don't see corresponding decrease in munmap.
Yup, same issue in mainline, it seems. I'll drop it.
> a > e27540595d282 md/raid5: fix soft lockup in retry_aligned_read()
> ! check_mul_overflow -- is it generic for all types? does sizeof > return size_t?...? > 16b4cbdf426d7 lib/ts_kmp: fix integer overflow in pattern length calculation
>
> + unsigned int prefix_tbl_len;
> + if (unlikely(check_mul_overflow(len, sizeof(*kmp->prefix_tbl),
> + &prefix_tbl_len) ||
>
> AFAICT sizeof returns size_t, so I'd be much if prefix_tbl_len was
> size_t, too.
Fair enough, but that's how it is in mainline, and unless there is something actually broken I'd prefer to keep it that way to avoid conflicts with future patches.
CU
Uli
next prev parent reply other threads:[~2026-07-14 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 13:50 Request for review for 4.4-st78, 4.4-cip113 Ulrich Hecht
2026-07-13 10:37 ` Pavel Machek
2026-07-14 20:47 ` Ulrich Hecht [this message]
2026-07-14 6:43 ` nobuhiro.iwamatsu.x90
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=1138844765.324155.1784062046046@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.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