Re: [PATCH v5 01/13] taint: Introduce a new taint flag (insecure)

2019-02-05 Thread hpa
On February 5, 2019 2:46:11 PM PST, Randy Dunlap wrote: >On 2/5/19 1:21 PM, Andrew Morton wrote: >> On Fri, 1 Feb 2019 18:42:29 -0800 Andy Lutomirski >wrote: >> >>> On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae > wrote: For testing (or root-only) purposes, the new flag will serve to

Re: [PATCH v5 01/13] taint: Introduce a new taint flag (insecure)

2019-02-05 Thread Randy Dunlap
On 2/5/19 1:21 PM, Andrew Morton wrote: > On Fri, 1 Feb 2019 18:42:29 -0800 Andy Lutomirski wrote: > >> On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae >> wrote: >>> >>> For testing (or root-only) purposes, the new flag will serve to tag the >>> kernel taint accurately. >>> >>> When adding a new

Re: [PATCH v5 01/13] taint: Introduce a new taint flag (insecure)

2019-02-05 Thread Andrew Morton
On Fri, 1 Feb 2019 18:42:29 -0800 Andy Lutomirski wrote: > On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote: > > > > For testing (or root-only) purposes, the new flag will serve to tag the > > kernel taint accurately. > > > > When adding a new feature support, patches need to be incrementally

Re: [PATCH v5 01/13] taint: Introduce a new taint flag (insecure)

2019-02-01 Thread Andy Lutomirski
On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote: > > For testing (or root-only) purposes, the new flag will serve to tag the > kernel taint accurately. > > When adding a new feature support, patches need to be incrementally > applied and tested with temporal parameters. Currently, there is no

[PATCH v5 01/13] taint: Introduce a new taint flag (insecure)

2019-02-01 Thread Chang S. Bae
For testing (or root-only) purposes, the new flag will serve to tag the kernel taint accurately. When adding a new feature support, patches need to be incrementally applied and tested with temporal parameters. Currently, there is no flag for this usage. Suggested-by: H. Peter Anvin