First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2016 The Android Open Source Project
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
2016-12-20 08:18:32 -08:00
|
|
|
#include <frameworks/base/core/proto/android/os/incident.pb.h>
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
|
|
|
|
#include <map>
|
2017-08-15 22:01:41 -07:00
|
|
|
#include <string>
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
using namespace android;
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
using namespace android::os;
|
|
|
|
using namespace google::protobuf;
|
|
|
|
using namespace google::protobuf::io;
|
|
|
|
using namespace google::protobuf::internal;
|
|
|
|
using namespace std;
|
|
|
|
|
2017-08-18 14:51:20 -07:00
|
|
|
static inline void emptyline() {
|
|
|
|
printf("\n");
|
|
|
|
}
|
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
static void generateHead(const char* header) {
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
printf("// Auto generated file. Do not modify\n");
|
2017-08-18 14:51:20 -07:00
|
|
|
emptyline();
|
2017-08-15 22:01:41 -07:00
|
|
|
printf("#include \"%s.h\"\n", header);
|
2017-08-18 14:51:20 -07:00
|
|
|
emptyline();
|
2017-08-15 22:01:41 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
// ================================================================================
|
2017-08-18 14:51:20 -07:00
|
|
|
static bool generateIncidentSectionsCpp(Descriptor const* descriptor)
|
2017-08-15 22:01:41 -07:00
|
|
|
{
|
|
|
|
generateHead("incident_sections");
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
map<string,FieldDescriptor const*> sections;
|
|
|
|
int N;
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
N = descriptor->field_count();
|
|
|
|
for (int i=0; i<N; i++) {
|
|
|
|
const FieldDescriptor* field = descriptor->field(i);
|
|
|
|
if (field->type() == FieldDescriptor::TYPE_MESSAGE) {
|
|
|
|
sections[field->name()] = field;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
printf("IncidentSection const INCIDENT_SECTIONS[] = {\n");
|
|
|
|
N = sections.size();
|
|
|
|
int i = 0;
|
|
|
|
for (map<string,FieldDescriptor const*>::const_iterator it = sections.begin();
|
|
|
|
it != sections.end(); it++, i++) {
|
|
|
|
const FieldDescriptor* field = it->second;
|
|
|
|
printf(" { %d, \"%s\" }", field->number(), field->name().c_str());
|
|
|
|
if (i != N-1) {
|
|
|
|
printf(",\n");
|
|
|
|
} else {
|
|
|
|
printf("\n");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
printf("};\n");
|
|
|
|
|
|
|
|
printf("const int INCIDENT_SECTION_COUNT = %d;\n", N);
|
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
// ================================================================================
|
|
|
|
static void splitAndPrint(const string& args) {
|
|
|
|
size_t base = 0;
|
|
|
|
size_t found;
|
|
|
|
while (true) {
|
|
|
|
found = args.find_first_of(" ", base);
|
|
|
|
if (found != base) {
|
|
|
|
string arg = args.substr(base, found - base);
|
|
|
|
printf(" \"%s\",", arg.c_str());
|
|
|
|
}
|
|
|
|
if (found == args.npos) break;
|
|
|
|
base = found + 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-09-05 15:50:58 -07:00
|
|
|
static const std::string replaceAll(const string& field_name, const char oldC, const string& newS) {
|
2017-08-18 14:51:20 -07:00
|
|
|
if (field_name.find_first_of(oldC) == field_name.npos) return field_name.c_str();
|
|
|
|
size_t pos = 0, idx = 0;
|
|
|
|
char* res = new char[field_name.size() * newS.size() + 1]; // assign a larger buffer
|
|
|
|
while (pos != field_name.size()) {
|
|
|
|
char cur = field_name[pos++];
|
|
|
|
if (cur != oldC) {
|
|
|
|
res[idx++] = cur;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (size_t i=0; i<newS.size(); i++) {
|
|
|
|
res[idx++] = newS[i];
|
|
|
|
}
|
|
|
|
}
|
|
|
|
res[idx] = '\0';
|
2017-09-05 15:50:58 -07:00
|
|
|
std::string result(res);
|
|
|
|
delete [] res;
|
|
|
|
return result;
|
2017-08-18 14:51:20 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline bool isDefaultDest(const FieldDescriptor* field) {
|
|
|
|
return field->options().GetExtension(privacy).dest() == PrivacyFlags::default_instance().dest();
|
|
|
|
}
|
|
|
|
|
|
|
|
// Returns true if the descriptor doesn't have any non default privacy flags set, including its submessages
|
|
|
|
static bool generatePrivacyFlags(const Descriptor* descriptor, const char* alias, map<string, bool> &msgNames) {
|
|
|
|
bool hasDefaultFlags[descriptor->field_count()];
|
|
|
|
// iterate though its field and generate sub flags first
|
|
|
|
for (int i=0; i<descriptor->field_count(); i++) {
|
|
|
|
hasDefaultFlags[i] = true; // set default to true
|
|
|
|
const FieldDescriptor* field = descriptor->field(i);
|
2017-09-05 15:50:58 -07:00
|
|
|
const std::string field_name_str = replaceAll(field->full_name(), '.', "__");
|
|
|
|
const char* field_name = field_name_str.c_str();
|
2017-08-18 14:51:20 -07:00
|
|
|
// check if the same name is already defined
|
|
|
|
if (msgNames.find(field_name) != msgNames.end()) {
|
|
|
|
hasDefaultFlags[i] = msgNames[field_name];
|
|
|
|
continue;
|
|
|
|
};
|
|
|
|
|
|
|
|
PrivacyFlags p = field->options().GetExtension(privacy);
|
|
|
|
|
|
|
|
switch (field->type()) {
|
|
|
|
case FieldDescriptor::TYPE_MESSAGE:
|
|
|
|
if (generatePrivacyFlags(field->message_type(), field_name, msgNames) &&
|
|
|
|
isDefaultDest(field)) break;
|
|
|
|
|
2017-09-12 20:00:25 -07:00
|
|
|
printf("Privacy %s { %d, %d, %s_LIST, %d, NULL };\n", field_name, field->number(), field->type(), field_name, p.dest());
|
2017-08-18 14:51:20 -07:00
|
|
|
hasDefaultFlags[i] = false;
|
|
|
|
break;
|
|
|
|
case FieldDescriptor::TYPE_STRING:
|
|
|
|
if (isDefaultDest(field) && p.patterns_size() == 0) break;
|
|
|
|
|
2017-08-25 18:11:58 -07:00
|
|
|
printf("const char* %s_patterns[] = {\n", field_name);
|
2017-08-18 14:51:20 -07:00
|
|
|
for (int i=0; i<p.patterns_size(); i++) {
|
|
|
|
// the generated string need to escape backslash as well, need to dup it here
|
2017-09-05 15:50:58 -07:00
|
|
|
printf(" \"%s\",\n", replaceAll(p.patterns(i), '\\', "\\\\").c_str());
|
2017-08-18 14:51:20 -07:00
|
|
|
}
|
|
|
|
printf(" NULL };\n");
|
2017-09-12 20:00:25 -07:00
|
|
|
printf("Privacy %s { %d, %d, NULL, %d, %s_patterns };\n", field_name, field->number(), field->type(), p.dest(), field_name);
|
2017-08-18 14:51:20 -07:00
|
|
|
hasDefaultFlags[i] = false;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
if (isDefaultDest(field)) break;
|
2017-09-12 20:00:25 -07:00
|
|
|
printf("Privacy %s { %d, %d, NULL, %d, NULL };\n", field_name, field->number(), field->type(), p.dest());
|
2017-08-18 14:51:20 -07:00
|
|
|
hasDefaultFlags[i] = false;
|
|
|
|
}
|
|
|
|
// add the field name to message map, true means it has default flags
|
|
|
|
msgNames[field_name] = hasDefaultFlags[i];
|
|
|
|
}
|
|
|
|
|
|
|
|
bool allDefaults = true;
|
|
|
|
for (int i=0; i<descriptor->field_count(); i++) {
|
|
|
|
allDefaults &= hasDefaultFlags[i];
|
|
|
|
}
|
|
|
|
if (allDefaults) return true;
|
|
|
|
|
|
|
|
emptyline();
|
2017-09-12 20:00:25 -07:00
|
|
|
|
|
|
|
bool needConst = strcmp(alias, "PRIVACY_POLICY") == 0;
|
|
|
|
int policyCount = 0;
|
|
|
|
|
|
|
|
printf("%s Privacy* %s_LIST[] = {\n", needConst ? "const" : "", alias);
|
2017-08-18 14:51:20 -07:00
|
|
|
for (int i=0; i<descriptor->field_count(); i++) {
|
|
|
|
const FieldDescriptor* field = descriptor->field(i);
|
|
|
|
if (hasDefaultFlags[i]) continue;
|
2017-09-05 15:50:58 -07:00
|
|
|
printf(" &%s,\n", replaceAll(field->full_name(), '.', "__").c_str());
|
2017-09-12 20:00:25 -07:00
|
|
|
policyCount++;
|
|
|
|
}
|
|
|
|
if (needConst) {
|
|
|
|
printf("};\n\n");
|
|
|
|
printf("const int PRIVACY_POLICY_COUNT = %d;\n", policyCount);
|
|
|
|
} else {
|
|
|
|
printf(" NULL };\n");
|
2017-08-18 14:51:20 -07:00
|
|
|
}
|
|
|
|
emptyline();
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool generateSectionListCpp(Descriptor const* descriptor) {
|
2017-08-15 22:01:41 -07:00
|
|
|
generateHead("section_list");
|
|
|
|
|
2017-08-18 14:51:20 -07:00
|
|
|
// generates SECTION_LIST
|
2017-08-15 22:01:41 -07:00
|
|
|
printf("const Section* SECTION_LIST[] = {\n");
|
|
|
|
for (int i=0; i<descriptor->field_count(); i++) {
|
|
|
|
const FieldDescriptor* field = descriptor->field(i);
|
|
|
|
|
|
|
|
if (field->type() != FieldDescriptor::TYPE_MESSAGE) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
const SectionFlags s = field->options().GetExtension(section);
|
|
|
|
switch (s.type()) {
|
|
|
|
case SECTION_NONE:
|
|
|
|
continue;
|
|
|
|
case SECTION_FILE:
|
|
|
|
printf(" new FileSection(%d, \"%s\"),\n", field->number(), s.args().c_str());
|
|
|
|
break;
|
|
|
|
case SECTION_COMMAND:
|
|
|
|
printf(" new CommandSection(%d,", field->number());
|
|
|
|
splitAndPrint(s.args());
|
|
|
|
printf(" NULL),\n");
|
|
|
|
break;
|
|
|
|
case SECTION_DUMPSYS:
|
|
|
|
printf(" new DumpsysSection(%d,", field->number());
|
|
|
|
splitAndPrint(s.args());
|
|
|
|
printf(" NULL),\n");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2017-08-18 14:51:20 -07:00
|
|
|
printf(" NULL };\n");
|
|
|
|
emptyline();
|
|
|
|
|
|
|
|
// generates PRIVACY_POLICY
|
|
|
|
map<string, bool> messageNames;
|
|
|
|
if (generatePrivacyFlags(descriptor, "PRIVACY_POLICY", messageNames)) {
|
|
|
|
// if no privacy options set at all, define an empty list
|
2017-09-12 20:00:25 -07:00
|
|
|
printf("const Privacy* PRIVACY_POLICY_LIST[] = {};\n");
|
|
|
|
printf("const int PRIVACY_POLICY_COUNT = 0;\n");
|
2017-08-18 14:51:20 -07:00
|
|
|
}
|
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
// ================================================================================
|
|
|
|
int main(int argc, char const *argv[])
|
|
|
|
{
|
|
|
|
if (argc != 2) return 1;
|
|
|
|
const char* module = argv[1];
|
|
|
|
|
2017-08-18 14:51:20 -07:00
|
|
|
Descriptor const* descriptor = IncidentProto::descriptor();
|
|
|
|
|
2017-08-15 22:01:41 -07:00
|
|
|
if (strcmp(module, "incident") == 0) {
|
2017-08-18 14:51:20 -07:00
|
|
|
return !generateIncidentSectionsCpp(descriptor);
|
2017-08-15 22:01:41 -07:00
|
|
|
}
|
|
|
|
if (strcmp(module, "incidentd") == 0 ) {
|
2017-08-18 14:51:20 -07:00
|
|
|
return !generateSectionListCpp(descriptor);
|
2017-08-15 22:01:41 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
// return failure if not called by the whitelisted modules
|
|
|
|
return 1;
|
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
2016-11-21 17:51:35 -08:00
|
|
|
}
|