Hello! On Apr 20, 2009, at 6:04 PM, Lukas Hejtmanek wrote:
> On Mon, Apr 20, 2009 at 02:42:40PM -0600, Andreas Dilger wrote: >>> The core looks like this: >>> #1 0x00002b7d5ff825a2 in DumpModeDecode (tif=0x58cdd0, >>> buf=0xf7f7f7f5f5f5f6f6 >>> <Address 0xf7f7f7f5f5f5f6f6 out of bounds>, cc=76800, s=2016) >>> at tif_dumpmode.c:85 >> This looks like the buffer being passed to the kernel is not aligned >> properly. The message is fairly clear: >> buf=0xf7f7f7f5f5f5f6f6 >> <Address 0xf7f7f7f5f5f5f6f6 out of bounds> >> For mmap IO this should be aligned to a PAGE_SIZE boundary, normally >> a multiple of 4096 bytes. > the buffer had the valid value buf=0x5923a0 but it was > asynchronously modified > by someone to the value buf=0xf7f7f7f5f5f5f6f6. Actually sometimes gdb prints nonsense values like this in output for some reason that is beyond me, even though the buffer is valid. > so, what I see, there happens some memory corruption if using mmap > with lustre. Do you happen to have a simple reproducer that we can run and reproduce the issue? Please create a bug in our bugzilla with the reproducer attached. Thanks for the report. Bye, Oleg _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss