Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Ragile]Adapt kernel 5.10 for broadcom on the 202211 branch #14510

Draft
wants to merge 3 commits into
base: 202211
Choose a base branch
from

Conversation

pettershao-ragilenetworks
Copy link
Contributor

@pettershao-ragilenetworks pettershao-ragilenetworks commented Apr 4, 2023

Why I did it

Adapt kernel 5.10 for broadcom on the 202211 branch

How I did it

Adapt kernel 5.10 for broadcom on the 202211 branch

How to verify it

show version
docker ps -a
show platform syseeprom
show platform fan
show platform psustatus
show platform temperature
show platform firmware status
show platform ssdhealth
show interface status
show interface transceiver presence
show interface transceiver eeprom
show environment
sensors
sudo show system-health detail

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Description for the changelog

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: pettershao-ragilenetworks <pettershao@ragilenetworks.com>
@pettershao-ragilenetworks pettershao-ragilenetworks changed the title Adapt kernel 5.10 for broadcom on the 202211 branch [Platform/Ragile]Adapt kernel 5.10 for broadcom on the 202211 branch Apr 6, 2023
@pettershao-ragilenetworks pettershao-ragilenetworks changed the title [Platform/Ragile]Adapt kernel 5.10 for broadcom on the 202211 branch [Ragile]Adapt kernel 5.10 for broadcom on the 202211 branch Apr 11, 2023
@pettershao-ragilenetworks
Copy link
Contributor Author

There is no defaultxml in this SONiC OS, so we can ignore the error message of semgrep.

device/ragile/x86_64-ragile_ra-b[65](https://github.com/sonic-net/sonic-buildimage/actions/runs/4562122647/jobs/8048918057?pr=14465#step:4:66)10-32c-r0/monitor.py 
     python.lang.security.use-defused-xml.use-defused-xml
        The Python documentation recommends using `defusedxml` instead of `xml` because the native
        Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can
        leak confidential data and "XML bombs" can cause denial of service.
        Details: https://sg.run/kX47

          7┆ import xml.etree.ElementTree as ET

Signed-off-by: pettershao-ragilenetworks <pettershao@ragilenetworks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant