-
Notifications
You must be signed in to change notification settings - Fork 13
Misc fixes of PR #24 #29
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
Conversation
Signed-off-by: Gris Ge <fge@redhat.com>
Signed-off-by: Gris Ge <fge@redhat.com>
Summary of ChangesHello @cathay4t, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on a series of miscellaneous fixes and internal refactorings within the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request primarily consists of code formatting changes and dependency updates. While reviewing, I identified a critical pre-existing issue in src/eeprom/attr.rs where the Parseable implementation for EthtoolModuleEEPROMAttr was incomplete, causing several attributes to be parsed incorrectly. I've provided a detailed comment and a code suggestion to fix this bug. The other changes are stylistic and improve code consistency.
| ETHTOOL_A_MODULE_EEPROM_DATA => Self::Data(Vec::from(payload)), | ||
| kind => Self::Other(DefaultNla::parse(buf).context(format!( | ||
| "invalid ethtool module eeprom NLA kind {kind}" | ||
| ))?), | ||
| }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Parseable implementation for EthtoolModuleEEPROMAttr is incomplete. It's missing handlers for ETHTOOL_A_MODULE_EEPROM_OFFSET, ETHTOOL_A_MODULE_EEPROM_LENGTH, ETHTOOL_A_MODULE_EEPROM_PAGE, ETHTOOL_A_MODULE_EEPROM_BANK, and ETHTOOL_A_MODULE_EEPROM_I2C_ADDRESS. This will cause these attributes to be incorrectly parsed as EthtoolModuleEEPROMAttr::Other when they are present in a netlink message from the kernel. This is a critical issue as it prevents correct parsing of ETHTOOL_MSG_MODULE_EEPROM_GET_REPLY messages.
ETHTOOL_A_MODULE_EEPROM_OFFSET => Self::Offset(
netlink_packet_core::parse_u32(payload)
.context("invalid ETHTOOL_A_MODULE_EEPROM_OFFSET value")?,
),
ETHTOOL_A_MODULE_EEPROM_LENGTH => Self::Length(
netlink_packet_core::parse_u32(payload)
.context("invalid ETHTOOL_A_MODULE_EEPROM_LENGTH value")?,
),
ETHTOOL_A_MODULE_EEPROM_PAGE => {
if payload.len() != 1 {
return Err(DecodeError::from(
"invalid ETHTOOL_A_MODULE_EEPROM_PAGE value: length is not 1",
));
}
Self::Page(payload[0])
}
ETHTOOL_A_MODULE_EEPROM_BANK => {
if payload.len() != 1 {
return Err(DecodeError::from(
"invalid ETHTOOL_A_MODULE_EEPROM_BANK value: length is not 1",
));
}
Self::Bank(payload[0])
}
ETHTOOL_A_MODULE_EEPROM_I2C_ADDRESS => {
if payload.len() != 1 {
return Err(DecodeError::from(
"invalid ETHTOOL_A_MODULE_EEPROM_I2C_ADDRESS value: length is not 1",
));
}
Self::I2CAddress(payload[0])
}
ETHTOOL_A_MODULE_EEPROM_DATA => Self::Data(Vec::from(payload)),
kind => Self::Other(DefaultNla::parse(buf).context(format!(
"invalid ethtool module eeprom NLA kind {kind}"
))?),
})
No description provided.