- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1.6k
 
Feature: Implement WRITE support in nfs2 Task: #4946 #14111
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
| 
           NOTE: This PR may contain new authors.  | 
    
          Codecov Report❌ Patch coverage is  Additional details and impacted files@@            Coverage Diff             @@
##             main   #14111      +/-   ##
==========================================
- Coverage   84.46%   84.46%   -0.01%     
==========================================
  Files        1013     1013              
  Lines      271932   271958      +26     
==========================================
+ Hits       229694   229708      +14     
- Misses      42238    42250      +12     
 Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
  | 
    
| 
           Commit message should meet our requirements, can you update it? What pcap did you test with? I didn't see one in the ticket and there is no Suricata-Verify test.  | 
    
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.
To Victor's point, could you please create Suricata-verify tests to accompany this work?
Thanks in advance :)
| }; | ||
| nfs_status = stat; | ||
| } | ||
| 
               | 
          
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.
Why this extra line here?
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.
oooh, that was a typo. will work on that.
          
 thanks for the review, lemme work on the suggested changes.  | 
    
| 
           Can you answer the question about the pcap/SV test?  | 
    
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.
Git message needs to meet our guidelines
          
  | 
    
          
 hello Victor, this PR here is a follow-up of the requested changes.  | 
    
| 
           Replaced w #14171 Hey @kaddujames501-ship-it ! Please close any old PRs once you have created a new one w feedback incorporated. Thank you! :)  | 
    
Issue #4946
Make sure these boxes are checked accordingly before submitting your Pull Request -- thank you.
Contribution style:
https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html
Our Contribution agreements:
https://suricata.io/about/contribution-agreement/ (note: this is only required once)
Changes (if applicable):
https://redmine.openinfosecfoundation.org/projects/suricata/issues
Link to ticket: https://redmine.openinfosecfoundation.org/issues/4946
Describe changes:
Provide values to any of the below to override the defaults.
link to the pull request in the respective
_BRANCHvariable.SV_REPO=
SV_BRANCH=
SU_REPO=
SU_BRANCH=
James Kaddu: [email protected]