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

Datasets locking/v7 #12366

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

inashivb
Copy link
Member

@inashivb inashivb commented Jan 9, 2025

Link to ticket: https://redmine.openinfosecfoundation.org/issues/7398

Previous PR: #12361

Changes since v6:

  • no logical changes

SV_BRANCH=OISF/suricata-verify#2225

In a recent warning reported by scan-build, datasets were found to be
using a blocking call in a critical section.

datasets.c:187:12: warning: Call to blocking function 'fgets' inside of critical section [unix.BlockInCriticalSection]
  187 |     while (fgets(line, (int)sizeof(line), fp) != NULL) {
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datasets.c:292:12: warning: Call to blocking function 'fgets' inside of critical section [unix.BlockInCriticalSection]
  292 |     while (fgets(line, (int)sizeof(line), fp) != NULL) {
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datasets.c:368:12: warning: Call to blocking function 'fgets' inside of critical section [unix.BlockInCriticalSection]
  368 |     while (fgets(line, (int)sizeof(line), fp) != NULL) {
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datasets.c:442:12: warning: Call to blocking function 'fgets' inside of critical section [unix.BlockInCriticalSection]
  442 |     while (fgets(line, (int)sizeof(line), fp) != NULL) {
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datasets.c:512:12: warning: Call to blocking function 'fgets' inside of critical section [unix.BlockInCriticalSection]
  512 |     while (fgets(line, (int)sizeof(line), fp) != NULL) {
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5 warnings generated.

These calls are blocking in the multi tenant mode where several tenants
may be trying to load the same dataset in parallel.
In a single tenant mode, this operation is performed as a part of a
single thread before the engine startup.

In order to evade the warning and simplify the code, the initial file
reading is moved to Rust with this commit with a much simpler handling
of dataset and datarep.

Bug 7398
Copy link

codecov bot commented Jan 9, 2025

Codecov Report

Attention: Patch coverage is 88.11881% with 12 lines in your changes missing coverage. Please review.

Project coverage is 82.50%. Comparing base (494d7bf) to head (90b9c5a).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #12366      +/-   ##
==========================================
- Coverage   82.54%   82.50%   -0.05%     
==========================================
  Files         912      913       +1     
  Lines      258028   258074      +46     
==========================================
- Hits       212988   212917      -71     
- Misses      45040    45157     +117     
Flag Coverage Δ
fuzzcorpus 60.56% <24.75%> (-0.16%) ⬇️
livemode 19.39% <0.00%> (-0.01%) ⬇️
pcap 44.35% <0.00%> (-0.07%) ⬇️
suricata-verify 63.21% <98.88%> (+0.02%) ⬆️
unittests 58.09% <0.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 24154

}

#[no_mangle]
pub unsafe extern "C" fn ProcessStringDatasets(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we handle all other types as well in rust to fully address the issue?

// Defined in util-debug.c
/// cbindgen:ignore
extern {
pub fn CallbackFatalErrorOnInit(arg: *const c_char);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jasonish should we create a 'public' SCFatalErrorOnInit instead?

Also, would like it to behave like FatalError and SCLog... to take a format string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants