Bug 9249 - patchwork: test that CVE patches contain the proper formatting
Summary: patchwork: test that CVE patches contain the proper formatting
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchwork (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2 M2
Assignee: Mariano Lopez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-03-14 15:05 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-12-06 16:52 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo Sandoval Gonzalez 2016-03-14 15:05:53 UTC 
CVE patchtes sent to the openembedded mailing list should be tested with patchtest/patchwork for proper format. Proper format at least means indicating the CVE number in the summary and the string 'CVE: CVE-<number>' in the patch description area. An example for correct formatting would be

http://patchwork.openembedded.org/patch/117791/
Comment 1 Leonardo Sandoval Gonzalez 2016-03-14 17:09:53 UTC 
A link that shows how to create a CVE patch:

http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#CVE_Patches
Comment 2 Leonardo Sandoval Gonzalez 2016-06-14 14:14:42 UTC 
Expected to be finished early 2.2M2.
Comment 3 Leonardo Sandoval Gonzalez 2016-06-23 19:51:52 UTC 
My fault, moving it to M1 again. CCB should agree on any milestone movement.
Comment 4 Leonardo Sandoval Gonzalez 2016-06-30 20:31:51 UTC 
This is already implemented but not tested.
Comment 5 Mariano Lopez 2016-07-11 13:19:26 UTC 
Sent patches to Leo
Comment 6 Leonardo Sandoval Gonzalez 2016-07-21 16:34:36 UTC 
This check is already implemented on the patchtest-oe suite. The way to validate this check is through 'selftest' implemented on patchtest-oe repo

+ clone patchtest and patchtest-oe (right now these are not public), follow patchtest-oe setup instructions
+ run the following cmd:
        cd $patchtest-oe/selftest; ./selftest
+ expected output: no output should be seen on console