From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] Request for reviews for 4.4-st38/4.4-cip73
Date: Mon, 13 Mar 2023 16:58:54 +0100 (CET) [thread overview]
Message-ID: <161763654.1591667.1678723134566@webmail.strato.com> (raw)
In-Reply-To: <ZApRDHkYvu2bOgZM@duo.ucw.cz>
Thanks for the reviews.
> On 03/09/2023 10:35 PM CET Pavel Machek <pavel@denx.de> wrote:
> I believe we should be taking this one. It is mostly theoretical bug,
> backport is extensive and we really have no way of testing it:
>
> ! syscaller -> theoretical bug. This would really need testing. They
> were deleting code from ack_complete. Lets... not? > 57059c01a09d nfc:
> pn533: Wait for out_urb's completion in pn533_usb_send_frame()
I have dropped this one...
> I'd cite commit # being backported on the first one, and I'll need to
> take second look at these:
>
> ! cite commit # of the patch being backported? > 7672af7c726f ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
...and added the commit reference.
CU
Uli
next prev parent reply other threads:[~2023-03-13 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:00 Request for reviews for 4.4-st38/4.4-cip73 Ulrich Hecht
2023-03-09 21:35 ` Pavel Machek
2023-03-13 15:58 ` Ulrich Hecht [this message]
[not found] ` <174ADDD3EF16CBFE.27660@lists.cip-project.org>
2023-03-10 10:09 ` [cip-dev] " Pavel Machek
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=161763654.1591667.1678723134566@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).