The size of cyclic buffer will be calculated automatically with
[PATCH 2/3], so users don't have to specify the size manually.
Signed-off-by: Atsushi Kumagai
---
makedumpfile.8 | 16
makedumpfile.c | 31 ++-
print_info.c | 11 ---
3 files ch
The size of cyclic buffer is set to DEFAULT_BUFSIZE_CYCLIC(1MB) when
the size isn't specified. But 1MB is too small for large memory machine
and the number of cycle will be so large. As a result, a lot of time
will be spend for dump filtering.
To resolve the issue above, I add calculate_cyclic_buf
get_free_memory_size() reads /proc/meminfo and consider "MemFree:"
the amount of free memory.
Signed-off-by: Atsushi Kumagai
---
makedumpfile.c | 34 ++
makedumpfile.h | 1 +
2 files changed, 35 insertions(+)
diff --git a/makedumpfile.c b/makedumpfile.c
index 11
Hello,
I made the patch set based on v1.5.1-beta to calculate the size of cyclic
buffer automatically.
In v1.5.0, users have to specify the buffer size depending on system memory
size with --cyclic-buffer option in order to get decent performance.
This patch set avoids the inconvenience above b
Vivek Goyal writes:
> On Thu, Nov 08, 2012 at 02:40:50PM -0500, Vivek Goyal wrote:
>> On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
>>
>> [..]
>>
>> Thnking more about executable signature verification, I have another
>> question.
>>
>> While verifyign the signature, we w
On Thu, 2012-11-08 at 14:40 -0500, Vivek Goyal wrote:
> On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
>
> [..]
>
> Thnking more about executable signature verification, I have another question.
>
> While verifyign the signature, we will have to read the whole executable
> in
On Thu, Nov 08, 2012 at 02:40:50PM -0500, Vivek Goyal wrote:
> On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
>
> [..]
>
> Thnking more about executable signature verification, I have another question.
>
> While verifyign the signature, we will have to read the whole executab
On Tue, Nov 06, 2012 at 03:51:59PM -0800, Eric W. Biederman wrote:
[..]
Thnking more about executable signature verification, I have another question.
While verifyign the signature, we will have to read the whole executable
in memory. That sounds bad as we are in kernel mode and will not be kill
The patch includes functionality for apimember and apigetrtype eppic
callback routines along with helper functions to fetch information
related to the member of the structure/union
Whenever a structure/union member is accessed inside the eppic macro,
eppic will query makedumpfile through call back
Eppic enables access to symbols in two ways. The first, is a more
natural mode in that it makes symbols available as fully typed
entities. The second, is generic and treats all symbols as an address
to data which then needs to be cast to the proper type explicitly. The
former obviously enables an e
libeppic will call apigetctype call back function whenever it
encounters a token in the eppic macro. The call back function will use
DWARF to query information related to the requested token and will
pass it back to eppic using libeppic API calls. If the token does not
exist, then apigetctype call
The memset function will be used to specify the virtual address
and the length of the data to be scrubbed in the dump file from
the eppic macro. makedumpfile will convert these requests into
filter_info nodes which will be enqueued for filtering. Existing
makedumpfile functionality reads the filter
This patch implements a series of apigetuint* call back functions
which are used to access data from the dump image. Eppic uses these
call back functions to fetch the actual value of the global variables.
This patch also adds other call back functions as a place holder which
will be implemented in
This patch extends the makedumpfile functionality to include eppic
language support. The patch initializes eppic and then loads and
executes the specified eppic macros.
This patch also includes "--eppic" option to makedumpfile command to
specify the eppic macro or the directory containing eppic ma
This patch contains routines which initialize eppic and register call
back function which will be called whenever a new eppic macro is loaded
using eppic_load() API. The registered call back function executes the
eppic macro as soon as it is loaded.
The -ltinfo is included in LIBS in the Makefile,
makedumpfile security key filtering enhancement - Add Eppic language
support (formerly known as SIAL) to specify rules to scrub data in a
dumpfile. Eppic was previously part of crash source code repository.
The following series of patches enhance the makedumpfile to provide
a more powerful way to
On kernels from v2.6.18 to v2.6.37, buddy page is marked by the
PG_buddy flag.
kernel version | PG_buddy
-- +-
v2.6.17 to v2.6.26 | 19
v2.6.27 to v2.6.37 | 19 if CONFIG_PAGEFLAGS_EXTEND=y
| 18 otherwise
Note for hard
Clearling bits on cyclic buffer can overrun the cyclic buffer
according to some combination of MAX_ORDER and cyclic buffer size.
This patch warns this possibility but continues processing.
Signed-off-by: HATAYAMA Daisuke
---
makedumpfile.c | 48 +++
This patch set implements filtering free pages looking up mem_map
array instead of free lists. This is compatible for cyclic mode
because looking up mem_map can be divided into cycles. On the other
hand, dividing free pages contaiend in free lists is difficult since
they are not sorted in physical-
On kernels from v2.6.15 to v2.6.17 buddy page is marked by the
condition that PG_private flag is set and _count == 0.
Unfortunately, I have yet to test this logic on these kernel versions
simply because I've been failing to boot them on my box.
Note that on these kernels, free list can be corrupt
On kernels from v2.6.38 and later kernels, buddy page is marked by
_mapcount == PAGE_BUDDY_MAPCOUNT_VALUE, which varies once as follows:
kernel version| PAGE_BUDDY_MAPCOUNT_VALUE
--+--
v2.6.38 | -2
v2.6.39 and later | -128
One more not
Add free page filtering logic in __exclude_unnecessary_pages.
Unlike other filtering levels, the number of free pages indicated by
buddy page is multiple. So I put this logic in the first position to
skip the pages corresponding to free pages.
This mem_map array logic is used in cyclic mode only.
This is need to determine if a specified enumeration type is present
in a given debug information.
In this patch set, I'll use this to check if enum pageflags is
present.
The newly introduced interface is a simple extension from the existing
one for enumeration value.
Signed-off-by: HATAYAMA Dai
Add new parameters required for mem_map-based freepages filtering, to
various tables.
Signed-off-by: HATAYAMA Daisuke
---
makedumpfile.h |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/makedumpfile.h b/makedumpfile.h
index 20f4d99..1304df0 100644
--- a/makedumpfi
Basically, these should be exported as VMCOREINFO from kernel. But we
cannot modify old kernels. Luckily, page flag values had frequently
changed in old kernels, so on old kernels, it's relatively easy to
determine appropreate page flags on a given kernel version without any
symbol and type informa
Page flags setup needs to be done after debuginfo initialization. We
use hard coded values only when debugging information doesn't provide
corresponding values.
Signed-off-by: HATAYAMA Daisuke
---
makedumpfile.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/makedu
Signed-off-by: HATAYAMA Daisuke
---
makedumpfile.c | 21 -
1 files changed, 20 insertions(+), 1 deletions(-)
diff --git a/makedumpfile.c b/makedumpfile.c
index 6513059..0d03716 100644
--- a/makedumpfile.c
+++ b/makedumpfile.c
@@ -914,6 +914,8 @@ get_structure_info(void)
27 matches
Mail list logo