| /linux/fs/gfs2/ |
| H A D | glops.h | 26 void gfs2_ail_flush(struct gfs2_glock *gl, bool fsync);
|
| H A D | file.c | 1600 .fsync = gfs2_fsync,
1615 .fsync = gfs2_fsync,
1634 .fsync = gfs2_fsync,
1647 .fsync = gfs2_fsync,
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 104 Say you want to test fsync on your file system. You would do something like
113 <some test that does fsync at the end>
114 dmsetup message log 0 mark fsync
119 replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync
|
| /linux/fs/ramfs/ |
| H A D | file-mmu.c | 45 .fsync = noop_fsync,
|
| /linux/tools/testing/selftests/ublk/ |
| H A D | common.c | 10 fsync(dev->fds[i]); in backing_file_tgt_deinit()
|
| /linux/sound/soc/codecs/ |
| H A D | cs42l42.c | 790 u32 fsync = sclk / sample_rate; in cs42l42_asp_config() local
793 if (((fsync * sample_rate) != sclk) || ((fsync % 2) != 0)) { in cs42l42_asp_config()
804 CS42L42_FRAC0_VAL(fsync - 1) << in cs42l42_asp_config()
809 CS42L42_FRAC1_VAL(fsync - 1) << in cs42l42_asp_config()
812 fsync = fsync / 2; in cs42l42_asp_config()
816 CS42L42_FRAC0_VAL(fsync - 1) << in cs42l42_asp_config()
821 CS42L42_FRAC1_VAL(fsync - 1) << in cs42l42_asp_config()
|
| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | errseq.rst | 22 最初的用例是跟踪文件同步系统调用（ ``fsync``, ``fdatasync``, ``msync`` 和
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | marvell,armada-370-pinctrl.txt | 26 mpp10 10 gpio, ge0(txctl), uart0(cts), tdm(fsync), audio(sdi)
84 mpp57 57 gpio, dev(cs3), uart1(rxd), tdm(fsync), sata0(prsnt),
|
| H A D | marvell,armada-375-pinctrl.txt | 37 mpp21 21 gpio, tdm(fsync)
|
| H A D | marvell,armada-xp-pinctrl.txt | 47 mpp26 26 gpio, lcd(clk), tdm(fsync)
|
| H A D | marvell,armada-39x-pinctrl.txt | 70 mpp49 49 gpio, sata2(prsnt) [2], sata3(prsnt) [2], tdm(fsync) [2],
|
| /linux/fs/ |
| H A D | aio.c | 201 struct fsync_iocb fsync; member
1695 struct aio_kiocb *iocb = container_of(work, struct aio_kiocb, fsync.work); in aio_fsync_work()
1697 scoped_with_creds(iocb->fsync.creds) in aio_fsync_work()
1698 iocb->ki_res.res = vfs_fsync(iocb->fsync.file, iocb->fsync.datasync); in aio_fsync_work()
1700 put_cred(iocb->fsync.creds); in aio_fsync_work()
1711 if (unlikely(!req->file->f_op->fsync)) in aio_fsync()
2065 return aio_fsync(&req->fsync, iocb, false); in __io_submit_one()
2067 return aio_fsync(&req->fsync, iocb, true); in __io_submit_one()
|
| /linux/Documentation/filesystems/ |
| H A D | overlayfs.rst | 804 The fsync(2) system call ensures that the data and metadata of a file
808 Without an fsync(2) call, there is no guarantee that the observed
816 ordering on storing changes without explicit fsync(2) calls, in case
819 experience, overlayfs calls fsync(2) on the upper file before completing
822 By default, overlayfs does not explicitly call fsync(2) on copied up
824 persist the user's modification unless the user calls fsync(2).
825 The fsync during copy up only guarantees that if a copy up is observed
830 fsync on a file also persists the parent directory changes, because they
836 to the underlying upper layer. This is controlled by the "fsync" mount
840 Call fsync(2) on upper file before completion of data copy up.
[all …]
|
| /linux/fs/smb/client/ |
| H A D | cifsfs.c | 1664 .fsync = cifs_fsync,
1684 .fsync = cifs_strict_fsync,
1704 .fsync = cifs_fsync,
1722 .fsync = cifs_fsync,
1740 .fsync = cifs_strict_fsync,
1758 .fsync = cifs_fsync,
1779 .fsync = cifs_dir_fsync,
|
| /linux/fs/orangefs/ |
| H A D | file.c | 476 new_op->upcall.req.fsync.refn = orangefs_inode->refn; in orangefs_fsync()
585 .fsync = orangefs_fsync,
|
| H A D | upcall.h | 252 struct orangefs_fsync_request_s fsync; member
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse-io.rst | 38 reclaim on memory pressure) or explicitly (invoked by close(2), fsync(2) and
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | arg_parsing.c | 147 if (!ASSERT_OK(fsync(fileno(fp)), "fsync tmp")) in test_parse_test_list_file()
|
| /linux/Documentation/translations/zh_CN/filesystems/ |
| H A D | ubifs-authentication.rst | 111 为避免闪存磨损，索引仅在满足特定条件（如 ``fsync(2)`` ）时才持久化（提交）。
|
| /linux/tools/testing/selftests/cachestat/ |
| H A D | test_cachestat.c | 176 } else if (fsync(fd)) { in test_cachestat()
|
| /linux/fs/qnx6/ |
| H A D | dir.c | 278 .fsync = simple_fsync,
|
| /linux/arch/powerpc/platforms/cell/spufs/ |
| H A D | inode.c | 213 .fsync = noop_fsync,
492 .fsync = noop_fsync,
|
| /linux/Documentation/block/ |
| H A D | writeback_cache_control.rst | 13 a data integrity operation like fsync, sync or an unmount.
|
| /linux/tools/testing/selftests/mm/ |
| H A D | memory-failure.c | 294 fsync(fd); in TEST_F()
|
| /linux/fs/coda/ |
| H A D | file.c | 329 .fsync = coda_fsync,
|