From: Johan Jonker <jbx6244@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, andy.yan@rock-chips.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, david.wu@rock-chips.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 1/2] ethernet: arc: fix the device for dma_map_single/dma_unmap_single
Date: Tue, 29 Oct 2024 15:53:26 +0100 [thread overview]
Message-ID: <f147c6c4-30e8-40cc-8a01-dc8df3913421@gmail.com> (raw)
In-Reply-To: <86192630-e09f-4392-9aca-9cc7e577107f@lunn.ch>
On 10/28/24 14:03, Andrew Lunn wrote:
> On Sun, Oct 27, 2024 at 10:41:48AM +0100, Johan Jonker wrote:
>> The ndev->dev and pdev->dev aren't the same device, use ndev->dev.parent
>> which has dma_mask, ndev->dev.parent is just pdev->dev.
>> Or it would cause the following issue:
>>
>> [ 39.933526] ------------[ cut here ]------------
>> [ 39.938414] WARNING: CPU: 1 PID: 501 at kernel/dma/mapping.c:149 dma_map_page_attrs+0x90/0x1f8
>>
>> Signed-off-by: David Wu <david.wu@rock-chips.com>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>
> A few process issues:
>
> For a patch set please add a patch 0/X which explains the big picture
> of what the patchset does. For a single patch, you don't need one.
>
> Please read:
>
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
>
> It is not clear which tree you intend these patches to be applied
> to. This one looks like it should be to net, but needs a Fixes:
> tag. The MDIO patch might be for net-next?
Hi Andrew, Andy,
My desktop setup has a problem compiling older kernels for rk3066 MK808 to verify.
Are you able to bisect/compile for rk3036 before this one:
====
commit bc0e610a6eb0d46e4123fafdbe5e6141d9fff3be (HEAD -> test1)
Author: Jianglei Nie <niejianglei2021@163.com>
Date: Wed Mar 9 20:18:24 2022 +0800
net: arc_emac: Fix use after free in arc_mdio_probe()
====
This is the oldest EMAC related checkout I can compile.
At that patch it still gives this warnings in the kernel log.
[ 16.678988] ------------[ cut here ]------------
[ 16.684189] WARNING: CPU: 0 PID: 809 at kernel/dma/mapping.c:151 dma_map_page_attrs+0x2b4/0x358
The driver was maintained on auto pilot recent years without a check by Rockchip users somehow.
Currently I don't know where and when this was introduced.
Please advise how to move forward. Should we just mark it net-next?
Johan
>
> Andrew
>
> ---
> pw-bot: cr
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, andy.yan@rock-chips.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, david.wu@rock-chips.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 1/2] ethernet: arc: fix the device for dma_map_single/dma_unmap_single
Date: Tue, 29 Oct 2024 15:53:26 +0100 [thread overview]
Message-ID: <f147c6c4-30e8-40cc-8a01-dc8df3913421@gmail.com> (raw)
In-Reply-To: <86192630-e09f-4392-9aca-9cc7e577107f@lunn.ch>
On 10/28/24 14:03, Andrew Lunn wrote:
> On Sun, Oct 27, 2024 at 10:41:48AM +0100, Johan Jonker wrote:
>> The ndev->dev and pdev->dev aren't the same device, use ndev->dev.parent
>> which has dma_mask, ndev->dev.parent is just pdev->dev.
>> Or it would cause the following issue:
>>
>> [ 39.933526] ------------[ cut here ]------------
>> [ 39.938414] WARNING: CPU: 1 PID: 501 at kernel/dma/mapping.c:149 dma_map_page_attrs+0x90/0x1f8
>>
>> Signed-off-by: David Wu <david.wu@rock-chips.com>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>
> A few process issues:
>
> For a patch set please add a patch 0/X which explains the big picture
> of what the patchset does. For a single patch, you don't need one.
>
> Please read:
>
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
>
> It is not clear which tree you intend these patches to be applied
> to. This one looks like it should be to net, but needs a Fixes:
> tag. The MDIO patch might be for net-next?
Hi Andrew, Andy,
My desktop setup has a problem compiling older kernels for rk3066 MK808 to verify.
Are you able to bisect/compile for rk3036 before this one:
====
commit bc0e610a6eb0d46e4123fafdbe5e6141d9fff3be (HEAD -> test1)
Author: Jianglei Nie <niejianglei2021@163.com>
Date: Wed Mar 9 20:18:24 2022 +0800
net: arc_emac: Fix use after free in arc_mdio_probe()
====
This is the oldest EMAC related checkout I can compile.
At that patch it still gives this warnings in the kernel log.
[ 16.678988] ------------[ cut here ]------------
[ 16.684189] WARNING: CPU: 0 PID: 809 at kernel/dma/mapping.c:151 dma_map_page_attrs+0x2b4/0x358
The driver was maintained on auto pilot recent years without a check by Rockchip users somehow.
Currently I don't know where and when this was introduced.
Please advise how to move forward. Should we just mark it net-next?
Johan
>
> Andrew
>
> ---
> pw-bot: cr
>
>
next prev parent reply other threads:[~2024-10-29 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 9:41 [PATCH v1 1/2] ethernet: arc: fix the device for dma_map_single/dma_unmap_single Johan Jonker
2024-10-27 9:41 ` Johan Jonker
2024-10-27 9:42 ` [PATCH v1 2/2] net: arc: rockchip: fix emac mdio node support Johan Jonker
2024-10-27 9:42 ` Johan Jonker
2024-10-27 9:58 ` Andy Yan
2024-10-27 9:58 ` Andy Yan
2024-10-28 12:59 ` [PATCH " Andrew Lunn
2024-10-28 12:59 ` Andrew Lunn
2024-10-29 8:22 ` Andy Yan
2024-10-29 8:22 ` Andy Yan
2024-10-29 12:46 ` Andrew Lunn
2024-10-29 12:46 ` Andrew Lunn
2024-10-28 13:03 ` [PATCH v1 1/2] ethernet: arc: fix the device for dma_map_single/dma_unmap_single Andrew Lunn
2024-10-28 13:03 ` Andrew Lunn
2024-10-29 14:53 ` Johan Jonker [this message]
2024-10-29 14:53 ` Johan Jonker
2024-10-30 0:19 ` Andy Yan
2024-10-30 0:19 ` Andy Yan
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=f147c6c4-30e8-40cc-8a01-dc8df3913421@gmail.com \
--to=jbx6244@gmail.com \
--cc=andrew@lunn.ch \
--cc=andy.yan@rock-chips.com \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.