File: vfs_wrapper_fuchsia.h

package info (click to toggle)
chromium 120.0.6099.224-1~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 6,112,112 kB
  • sloc: cpp: 32,907,025; ansic: 8,148,123; javascript: 3,679,536; python: 2,031,248; asm: 959,718; java: 804,675; xml: 617,256; sh: 111,417; objc: 100,835; perl: 88,443; cs: 53,032; makefile: 29,579; fortran: 24,137; php: 21,162; tcl: 21,147; sql: 20,809; ruby: 17,735; pascal: 12,864; yacc: 8,045; lisp: 3,388; lex: 1,323; ada: 727; awk: 329; jsp: 267; csh: 117; exp: 43; sed: 37
file content (27 lines) | stat: -rw-r--r-- 1,150 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
// Copyright 2019 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef SQL_VFS_WRAPPER_FUCHSIA_H_
#define SQL_VFS_WRAPPER_FUCHSIA_H_

#include "third_party/sqlite/sqlite3.h"

namespace sql {

// Fuchsia doesn't provide a file locking mechanism like flock(). These
// functions are used to simulate file locking. On Fuchsia profile directories
// are not expected to be shared with other processes and therefore only one
// browser process may access sqlite files. These functions are designed to
// handle the case when the same sqlite database is open more than once from the
// same browser process. In most cases databases do not need to be open more
// than once, i.e. contention is expected to be rare, so the main goal of the
// design is simplicity and not performance. The manager maintains a list of all
// currently locked files.
int Lock(sqlite3_file* sqlite_file, int file_lock);
int Unlock(sqlite3_file* sqlite_file, int file_lock);
int CheckReservedLock(sqlite3_file* sqlite_file, int* result);

}  // namespace sql

#endif  // SQL_VFS_WRAPPER_FUCHSIA_H_