unmap memory mapped with devm_ioremap_resource

[Valdis Kl=?utf-8?Q?=c4=93?=tnieks]

On Fri, 09 Dec 2022 12:58:20 -0700, jim.cromie at gmail.com said:
> On Fri, Dec 9, 2022 at 9:14 AM Adrian Fiergolski <adrian.fiergolski at fastree3d.com> wrote:
> > Does the community have any other ideas? Or I am wrong, and devm_iounmap is enough?

> I dunno, but it says you asked ~4 hrs ago.
> I bet you could just try it and get an answer faster.
> Do feel free to report back.

Note that it *is* possible for something to *look* like it works, but it leaves
dangling pointers or other hidden corruption that takes a while to surface.  I
once had to troubleshoot a userspace bug that worked fine on one system but
blew up on another with a different malloc() - some 6 million malloc calls
after the bug hit.

Fortunately, the vast majority of kernel functions will return an error code if
anything at all fishy happened, so just checking return codes on *everything* is
usually good enough...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 494 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20221209/3bc2a22e/attachment.sig>