From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: Re: [PATCH 5.10 000/131] 5.10.203-rc3 review
Date: Fri, 8 Dec 2023 07:47:29 +0100 [thread overview]
Message-ID: <2023120849-catalog-pretzel-ee8f@gregkh> (raw)
In-Reply-To: <efdb0591-2259-f86c-0da4-781dfdae22e1@ispras.ru>
On Thu, Dec 07, 2023 at 02:00:06AM +0300, Alexey Khoroshilov wrote:
> On 05.12.2023 22:22, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.203 release.
> > There are 131 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 07 Dec 2023 18:32:16 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.203-rc3.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> It seems something is seriously broken in this release.
>
> There are patches already applied in 5.10.202 that are in 5.10.203-rc3
> transformed in some strange way, e.g.
>
> Neil Armstrong <narmstrong@baylibre.com>
> tty: serial: meson: retrieve port FIFO size from DT
>
>
> commit 980c3135f1ae6fe686a70c8ba78eb1bb4bde3060 in 5.10.202
>
> diff --git a/drivers/tty/serial/meson_uart.c
> b/drivers/tty/serial/meson_uart.c
> index d06653493f0e..78bda91a6bf1 100644
> --- a/drivers/tty/serial/meson_uart.c
> +++ b/drivers/tty/serial/meson_uart.c
> @@ -728,6 +728,7 @@ static int meson_uart_probe(struct platform_device
> *pdev)
> {
> struct resource *res_mem, *res_irq;
> struct uart_port *port;
> + u32 fifosize = 64; /* Default is 64, 128 for EE UART_0 */
> int ret = 0;
>
> if (pdev->dev.of_node)
> @@ -755,6 +756,8 @@ static int meson_uart_probe(struct platform_device
> *pdev)
> if (!res_irq)
> return -ENODEV;
>
> + of_property_read_u32(pdev->dev.of_node, "fifo-size", &fifosize);
> +
> if (meson_ports[pdev->id]) {
> dev_err(&pdev->dev, "port %d already allocated\n",
> pdev->id);
> return -EBUSY;
> @@ -784,7 +787,7 @@ static int meson_uart_probe(struct platform_device
> *pdev)
> port->type = PORT_MESON;
> port->x_char = 0;
> port->ops = &meson_uart_ops;
> - port->fifosize = 64;
> + port->fifosize = fifosize;
>
> meson_ports[pdev->id] = port;
> platform_set_drvdata(pdev, port);
>
> vs.
>
> commit 71feab929585232694b4f2fb7d70abde4edc581e in 5.10.203-rc3
>
> diff --git a/drivers/tty/serial/meson_uart.c
> b/drivers/tty/serial/meson_uart.c
> index bb66a3f06626..c44ab21a9b7d 100644
> --- a/drivers/tty/serial/meson_uart.c
> +++ b/drivers/tty/serial/meson_uart.c
> @@ -765,6 +765,8 @@ static int meson_uart_probe(struct platform_device
> *pdev)
> of_property_read_u32(pdev->dev.of_node, "fifo-size", &fifosize);
> has_rtscts = of_property_read_bool(pdev->dev.of_node,
> "uart-has-rtscts");
>
> + of_property_read_u32(pdev->dev.of_node, "fifo-size", &fifosize);
> +
> if (meson_ports[pdev->id]) {
> dev_err(&pdev->dev, "port %d already allocated\n",
> pdev->id);
> return -EBUSY;
>
>
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE
>
>
>
> See also:
>
> Qu Huang <qu.huang@linux.dev>
> drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
>
> Axel Lin <axel.lin@ingics.com>
> i2c: sun6i-p2wi: Prevent potential division by zero
>
> Takashi Iwai <tiwai@suse.de>
> media: imon: fix access to invalid resource for the second interface
>
>
> Also there is a strange pair:
>
> Patrick Thompson <ptf@google.com>
> net: r8169: Disable multicast filter for RTL8168H and RTL8107E
>
> Heiner Kallweit <hkallweit1@gmail.com>
> Revert "net: r8169: Disable multicast filter for RTL8168H and RTL8107E"
>
Ok, I dropped all of these and manually verified that there were no
other duplicates. thanks for catching them and letting us know.
greg k-h
prev parent reply other threads:[~2023-12-08 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 19:22 [PATCH 5.10 000/131] 5.10.203-rc3 review Greg Kroah-Hartman
2023-12-05 22:01 ` Florian Fainelli
2023-12-06 1:55 ` Dominique Martinet
2023-12-06 11:37 ` Naresh Kamboju
2023-12-06 11:50 ` Jon Hunter
2023-12-06 16:31 ` Shuah Khan
2023-12-09 11:44 ` Greg Kroah-Hartman
2023-12-12 16:17 ` Shuah Khan
2023-12-06 23:00 ` Alexey Khoroshilov
2023-12-08 6:33 ` Greg Kroah-Hartman
2023-12-08 6:47 ` Greg Kroah-Hartman [this message]
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=2023120849-catalog-pretzel-ee8f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=lvc-project@linuxtesting.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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