Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix potential memory corruption#8

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ildus merged 1 commit intopostgrespro:masterfromasp437:master
Mar 15, 2018
Merged

Fix potential memory corruption#8

ildus merged 1 commit intopostgrespro:masterfromasp437:master
Mar 15, 2018

Conversation

asp437
Copy link
Contributor

I remove usage of old approach to configure background worker entry point sincepg_wait_sampling shouldn't work with PostgreSQL without support of new approach. It fixes potential usage of non-initializedbgw_main pointer which was introduced in#7 (it was my fault).
Also I replacedmemcpy call withsnprintf becausememcpy may read some uninitialized memory or try to read outside the segment/page after the string constants.

@funbringer
Copy link
Collaborator

Good catch! I've just spotted the same error in pg_pathman.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@asp437@funbringer@ildus

[8]ページ先頭

©2009-2025 Movatter.jp