[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <501533ad-7671-46aa-a034-91e0a6322e6c@moroto.mountain>
Date: Fri, 19 Jan 2024 11:25:51 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Niklas Cassel <Niklas.Cassel@....com>
Cc: Jingoo Han <jingoohan1@...il.com>,
Gustavo Pimentel <gustavo.pimentel@...opsys.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>
Subject: Re: [PATCH] PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq()
On Wed, Jan 17, 2024 at 09:21:41PM +0000, Niklas Cassel wrote:
> Hello Dan,
>
> On Wed, Jan 17, 2024 at 09:32:08PM +0300, Dan Carpenter wrote:
> > The "msg_addr" variable is u64. However, the "tbl_offset" is an unsigned
>
> Here you write tbl_offset.
>
> > int. This means that when the code does
> >
> > msg_addr &= ~aligned_offset;
> >
> > it will unintentionally zero out the high 32 bits. Declare "tbl_offset"
>
> Here you also write tbl_offset.
>
That's so weird... I can't imagine how that happened. Do you think it
could be a Welsh mice situation where forest creatures are changing my
work when I'm away from my desk? https://www.youtube.com/shorts/h8gkIbtaaek
Fixed in v2. Thanks!
regards,
dan carpenter
Powered by blists - more mailing lists