start_querying(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… start_querying(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the start_querying(9) page from the Kernel API Manual πŸŽ€ this is the glow-up moment where a hash lock finally gets to start deduplicating, and honestly? it's giving main character energy πŸ‘‘


🌸 NAME 🌸

start_querying β€” start deduplication for a hash lock πŸ’–


✨ SYNOPSIS ✨

void start_querying (struct hash_lock *lock , struct data_vio *data_vio );

like, that's the whole signature. no cap. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lock β€” the initialized hash lock πŸ’… (key word: initialized, she's ready, she's been prepped)
  • data_vio β€” the data_vio that has just obtained the new lock πŸ‘€ like it literally just walked in with the keys

🧚 DESCRIPTION 🧚

okay so here's the vibe 🌈 start_querying starts deduplication for a hash lock that has finished initializing. it does that by making the data_vio that requested it the agent, entering the QUERYING state, and then using that agent to perform the UDS query on behalf of the lock ✨

so basically: lock finishes initializing β†’ the data_vio that asked for it becomes the agent β†’ boom, we're in QUERYING β†’ agent goes and does the UDS query for the whole lock πŸŽ€ she's delegating. she's organized. she's iconic.

ngl the flow is: initialize β†’ promote a data_vio to agent β†’ state = QUERYING β†’ agent does the UDS query on the lock's behalf. that's the whole plot πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

buckle up bestie, this list is long β€” but every single one is here, fr fr πŸ’œ


and that's the page, bestie πŸ“ mwah πŸ’‹ this one came from ./drivers/md/dm-vdo and it's dated October 2026 ⭐ go read all 50-something of those SEE ALSO entries, i believe in you πŸ™ˆπŸ’œ

πŸ“¦ where this page comes from