Dear Mahesh,
ACK all three patches, tested, found no problem.
Sincerely,
Hoang
-Original Message-
From: mahesh.va...@oracle.com [mailto:mahesh.va...@oracle.com]
Sent: Tuesday, November 29, 2016 5:37 PM
To: hoang.m...@dektech.com.au; ramesh.bet...@oracle.com
Cc:
Hi Hoang,
We are some how able to simulated your test case.
Following are the detailed steps how we reproduced ,
this test is generating same core dumb as below.
But the provided patch resolved the issue, can you please test your self
provide your observations , if the test is different
Hi Hoang,
Can you please provide the snapshot of "df -h /dev/shm" when the issue
occurs.
Also.. can you please provide the corresponding core dump file and
"osafckptnd" process file (process file not required if this image is
build for SLES x86_64)
Thanks,
Ramesh.
On 11/30/2016 12:10 PM, Vo
Hi Hoang,
We have no option that , why because reproducible steps are not easy .
Please find the additional `2202_addtional.patch` patch on top of
published patch
this will confirm us it is completely not related to SHM free size.
-AVM
On 11/30/2016 12:10 PM, Vo Minh Hoang wrote:
Dear
Hi Hoang,
Thansk for the test .
Then it looks issue is not related to SHM deficiency ( 100 % used by
other application )
can you please re-test with below changes and that will confirm us it
is completely not related to SHM free size.
replacing:
`if (req->info.write.i_write_size >
Dear Mahesh,
Unfortunately, I have just receive information that the same core dump still
occur after applying patch.
Here is dump information in short, please tell me if I can do anything in
support:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fe314aa0109 in
Summary:leap : now leap library ensure shm availability before writing [#2202]
Review request for Trac Ticket(s): #2202
Peer Reviewer(s): Hoang / Ramesh
Pull request to: <>
Affected branch(es): <>
Development branch: <>
Impacted area Impact y/n
