-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pmem2: data_mover memory leak - pmem2_integration/TEST[39,41]: failed memcheck #5637
Labels
libpmem2
libpmem- and libpmem2-related
miniasync
async related issue
Priority: 3 medium
Type: Bug
A previously unknown bug in PMDK
Milestone
Comments
|
grom72
added a commit
to grom72/pmdk
that referenced
this issue
May 22, 2023
Disable pmem2_integration/TEST[39,41] with memcheck until pmem#5637 is fixed. Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
May 22, 2023
Disable pmem2_integration/TEST[39,41] with memcheck until pmem#5637 is fixed. Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
May 23, 2023
Automatically created data_mover is deleted during the map delete process. Fixes: pmem#5637 Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
May 23, 2023
Automatically created data_mover is deleted during the map delete process. Fixes: pmem#5637 Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
grom72
added a commit
to grom72/pmdk
that referenced
this issue
May 23, 2023
Automatically created data_mover is deleted during the map delete process. Fixes: pmem#5637 Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@intel.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
libpmem2
libpmem- and libpmem2-related
miniasync
async related issue
Priority: 3 medium
Type: Bug
A previously unknown bug in PMDK
ISSUE: pmem2: data_mover memory leak - pmem2_integration/TEST[39,41] failed under valgrind (self-hosted, rhel, RUNTESTS.py --force-enable memcheck)
Environment Information
Please provide a reproduction of the bug:
pmem2_integration/TEST39 failed under valgrind (self-hosted, rhel, RUNTESTS.py --force-enable memcheck)
wit error message:
fro page/byte configurations in all build types.
How often bug is revealed: (always, often, rare): always
Actual behavior:
Expected behavior:
Details
Additional information about Priority and Help Requested:
Are you willing to submit a pull request with a proposed change? (Yes, No)
Requested priority: (Showstopper, High, Medium, Low)
The text was updated successfully, but these errors were encountered: