Bug 1582

Summary: Host intrusion prevention/Swabber
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Richard Purdie <richard.purdie>
Component: meta-yoctoAssignee: Saul Wold <sgw>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Low CC: jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher, sgw, song.liu
Version: unspecified   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard: (No QA Needed Currently) Development (33% complete)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on: 822    
Bug Blocks:    

Description Richard Purdie 2011-10-03 15:17:18 UTC 
There are several issues:

* there are several recipes which don't work when run under strace with parallelisation. 
* it's not integrated into our process and tested regularly
* we have no known base data to compare against

We need to determine a path for inclusion of swabber into our process and execute on it so that we can be aware of and fix host intrusion issues.
Comment 1 Joshua Lock - Disabled 2011-10-19 18:46:18 UTC 
As a first stab at this I'd intend to deliver:

* A list of recipes which don't work when run under strace
* A report of known issues and a process (and if required, a tool) for comparing to the known base. 
* A plan for integration into our process and owning action of that plan

For later I'd like to see:

* Working with upstreams to fix the problematic recipes
Comment 2 Joshua Lock - Disabled 2011-11-09 11:30:51 UTC 
(In reply to comment #1)
> As a first stab at this I'd intend to deliver:
> * A list of recipes which don't work when run under strace

This should probably read "don't work well", namely - the recipes for which we have to explicitly disable parallelism in the swabber class (image-swab.bbclass).
Comment 3 Saul Wold 2011-11-15 10:42:48 UTC 
Design Signed Off
Comment 4 Song Liu 2011-11-28 10:30:09 UTC 
Moved this one to M2 as Josh has been busy working on point releases. His M2 schedule looks fine with this change.
Comment 5 Joshua Lock - Disabled 2011-12-21 17:14:37 UTC 
Having done some tidy up of this functionality I've discovered that the swabber report generation on larger are consuming large amounts of memory. ~6GB on a core-image-sato-sdk.

I think we need to hold off on further work on this feature until swabbers memory consumption has been reduced.
Comment 6 Saul Wold 2015-11-10 17:06:17 UTC 
Swabber is dead therefore closing this bug