diff options
| author | Phil Elwell <phil@raspberrypi.com> | 2024-04-01 14:09:33 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-05-17 12:43:51 +0300 |
| commit | c0edb6797bdfbeb975ab8367a368ccf4068802bd (patch) | |
| tree | 6432cdfcb1579ed8f66b7a110d9cdb5e839955ce /security/lsm_audit.c | |
| parent | 909859ed132df501bc32d12de3c802a05d2f7107 (diff) | |
| download | linux-c0edb6797bdfbeb975ab8367a368ccf4068802bd.tar.xz | |
net: bcmgenet: Reset RBUF on first open
[ Upstream commit 0a6380cb4c6b5c1d6dad226ba3130f9090f0ccea ]
If the RBUF logic is not reset when the kernel starts then there
may be some data left over from any network boot loader. If the
64-byte packet headers are enabled then this can be fatal.
Extend bcmgenet_dma_disable to do perform the reset, but not when
called from bcmgenet_resume in order to preserve a wake packet.
N.B. This different handling of resume is just based on a hunch -
why else wouldn't one reset the RBUF as well as the TBUF? If this
isn't the case then it's easy to change the patch to make the RBUF
reset unconditional.
See: https://github.com/raspberrypi/linux/issues/3850
See: https://github.com/raspberrypi/firmware/issues/1882
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Signed-off-by: Maarten Vanraes <maarten@rmail.be>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'security/lsm_audit.c')
0 files changed, 0 insertions, 0 deletions