Skip to content
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

SIGSEGV on HSCAN when field has a TTL #4799

Closed
tyrantlink opened this issue Mar 19, 2025 · 1 comment · Fixed by #4802
Closed

SIGSEGV on HSCAN when field has a TTL #4799

tyrantlink opened this issue Mar 19, 2025 · 1 comment · Fixed by #4802
Assignees
Labels
bug Something isn't working Next Up task that is ready to be worked on and should be added to working queue

Comments

@tyrantlink
Copy link

tyrantlink commented Mar 19, 2025

To Reproduce
Steps to reproduce the behavior:

  1. Insert and set TTL
HSET key field value
HEXPIRE key 120 FIELDS 1 field
  1. Call HSCAN
HSCAN key 0 match * count 500
  1. Dragonfly immediately crashes
*** SIGSEGV received at time=1742383416 on cpu 7 ***
PC: @     0x5564fa454908  (unknown)  std::_Function_handler<>::_M_invoke()

Expected behavior
HSCAN returns normal value, in the example case,

1) "0"
2) 1) "field"
   2) "value"

Environment (please complete the following information):

  • OS: Fedora Linux 41
  • Kernel: 6.13.6-200.fc41.x86_64
  • Containerized?: Podman (Docker)
  • Dragonfly Version: Latest (1.28.0)

Reproducible Code Snippet

HSET key field value
HEXPIRE key 120 FIELDS 1 field
HSCAN key 0 match * count 500

Additional context
Notably, Redis Insight will call HSCAN when viewing a hash, so simply viewing a hash that has ttl fields will cause dragonfly to crash.

@tyrantlink tyrantlink added the bug Something isn't working label Mar 19, 2025
@adiholden
Copy link
Collaborator

@tyrantlink thank you for reporting this

@adiholden adiholden added the Next Up task that is ready to be worked on and should be added to working queue label Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Next Up task that is ready to be worked on and should be added to working queue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants