~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/filesystems/dnotify.rst

Version: ~ [ linux-6.11.5 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.58 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.114 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.169 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.228 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.284 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.322 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.9 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/filesystems/dnotify.rst (Version linux-6.11.5) and /Documentation/filesystems/dnotify.rst (Version linux-2.6.32.71)


  1 .. SPDX-License-Identifier: GPL-2.0               
  2                                                   
  3 ============================                      
  4 Linux Directory Notification                      
  5 ============================                      
  6                                                   
  7            Stephen Rothwell <sfr@canb.auug.org.    
  8                                                   
  9 The intention of directory notification is to     
 10 to be notified when a directory, or any of the    
 11 The basic mechanism involves the application r    
 12 on a directory using a fcntl(2) call and the n    
 13 being delivered using signals.                    
 14                                                   
 15 The application decides which "events" it want    
 16 The currently defined events are:                 
 17                                                   
 18         =========       ======================    
 19         DN_ACCESS       A file in the director    
 20         DN_MODIFY       A file in the director    
 21         DN_CREATE       A file was created in     
 22         DN_DELETE       A file was unlinked fr    
 23         DN_RENAME       A file in the director    
 24         DN_ATTRIB       A file in the director    
 25                         changed (chmod,chown)     
 26         =========       ======================    
 27                                                   
 28 Usually, the application must reregister after    
 29 if DN_MULTISHOT is or'ed with the event mask,     
 30 remain until explicitly removed (by registerin    
 31                                                   
 32 By default, SIGIO will be delivered to the pro    
 33 information.  However, if the F_SETSIG fcntl(2    
 34 kernel know which signal to deliver, a siginfo    
 35 the signal handler and the si_fd member of tha    
 36 file descriptor associated with the directory     
 37                                                   
 38 Preferably the application will choose one of     
 39 (SIGRTMIN + <n>) so that the notifications may    
 40 especially important if DN_MULTISHOT is specif    
 41 is often blocked, so it is better to use (at l    
 42                                                   
 43 Implementation expectations (features and bugs    
 44 ----------------------------------------------    
 45                                                   
 46 The notification should work for any local acc    
 47 actual file system is on a remote server.  Thi    
 48 access to files served by local user mode serv    
 49 Also, remote accesses to files served by a loc    
 50 be notified.                                      
 51                                                   
 52 In order to make the impact on the file system    
 53 the problem of hard links to files has been ig    
 54 exists in two directories (a and b) then a cha    
 55 name "a/x" should be notified to a program exp    
 56 directory "a", but will not be notified to one    
 57 directory "b".                                    
 58                                                   
 59 Also, files that are unlinked, will still caus    
 60 last directory that they were linked to.          
 61                                                   
 62 Configuration                                     
 63 -------------                                     
 64                                                   
 65 Dnotify is controlled via the CONFIG_DNOTIFY c    
 66 disabled, fcntl(fd, F_NOTIFY, ...) will return    
 67                                                   
 68 Example                                           
 69 -------                                           
 70 See tools/testing/selftests/filesystems/dnotif    
 71                                                   
 72 NOTE                                              
 73 ----                                              
 74 Beginning with Linux 2.6.13, dnotify has been     
 75 See Documentation/filesystems/inotify.rst for     
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php