search for: fsnotify

https://bugzilla.mindrot.org/show_bug.cgi?id=2668 Bug ID: 2668 Summary: Implement event handler to launch external scripts Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: sftp-server Assignee:

d911d9874801 ("kernfs: make kernfs_notify() trigger inotify events too") added fsnotify triggering to kernfs_notify() which requires a sleepable context. There are already existing users of kernfs_notify() which invoke it from an atomic context and in general it's silly to require a sleepable context for triggering a notification. The following is an invalid context bug triggerd...

d911d9874801 ("kernfs: make kernfs_notify() trigger inotify events too") added fsnotify triggering to kernfs_notify() which requires a sleepable context. There are already existing users of kernfs_notify() which invoke it from an atomic context and in general it's silly to require a sleepable context for triggering a notification. The following is an invalid context bug triggerd...

On 06/29/2014 02:47 PM, Michael S. Tsirkin wrote: > On Sun, Jun 29, 2014 at 09:32:22PM +0200, Christoph Hellwig wrote: >> On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote: >>> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote: >>>> Hi All, >>>> >>>> We've had a report[1] of the virt_blk driver causing a lot of

On 06/29/2014 02:47 PM, Michael S. Tsirkin wrote: > On Sun, Jun 29, 2014 at 09:32:22PM +0200, Christoph Hellwig wrote: >> On Sun, Jun 29, 2014 at 11:26:37AM +0300, Michael S. Tsirkin wrote: >>> On Fri, Jun 27, 2014 at 07:57:38AM -0400, Josh Boyer wrote: >>>> Hi All, >>>> >>>> We've had a report[1] of the virt_blk driver causing a lot of

...2013] [<ffffffffa028dcf9>] ocfs2_file_aio_read+0xd9/0x3c0 [ocfs2] [Fri Oct 18 10:52:28 2013] [<ffffffff811ae425>] do_sync_readv_writev+0x65/0x90 [Fri Oct 18 10:52:28 2013] [<ffffffff811afba2>] do_readv_writev+0xd2/0x2b0 [Fri Oct 18 10:52:28 2013] [<ffffffff811eeda2>] ? fsnotify+0x1d2/0x2b0 [Fri Oct 18 10:52:28 2013] [<ffffffff811ae500>] ? do_sync_write+0xb0/0xb0 [Fri Oct 18 10:52:28 2013] [<ffffffff811f8886>] ? eventfd_write+0x1a6/0x210 [Fri Oct 18 10:52:28 2013] [<ffffffff811afe09>] vfs_readv+0x39/0x50 [Fri Oct 18 10:52:28 2013] [<ffffffff811b006...

...fffffffa0865e74>] vfio_pci_ioctl+0x314/0xa00 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? kmem_cache_alloc+0x1ba/0x1d0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 Oct 7 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? security_file_alloc+0x16/0x20 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio] Oct...

Is Inotify **fully supported** by OCFS2? Thank you

...gt; > > Josh, Brian, could you try reverting that commit to see if it helps? > > That definitely be a bug. If you need to block off ->bi_end_io(), just > must punt to a worker thread. Ugh... didn't realize we had users triggering sysfs notifications from an atomic context. fsnotify support requires sleepable context. Guess I'll have to punt it to a work item. :( Thanks. -- tejun

hi guys will we have gluster with inotify? some point / never? thanks, L.

On Tue, Jul 01, 2014 at 04:41:03PM -0400, Tejun Heo wrote: > d911d9874801 ("kernfs: make kernfs_notify() trigger inotify events > too") added fsnotify triggering to kernfs_notify() which requires a > sleepable context. There are already existing users of > kernfs_notify() which invoke it from an atomic context and in general > it's silly to require a sleepable context for triggering a > notification. > > The following is a...

...fffffffa0865e74>] vfio_pci_ioctl+0x314/0xa00 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? kmem_cache_alloc+0x1ba/0x1d0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 Oct 7 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? security_file_alloc+0x16/0x20 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio] Oct...

...o_pci_ioctl+0x314/0xa00 > [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? > kmem_cache_alloc+0x1ba/0x1d0 Oct 7 11:32:53 artemis2 kernel: > [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 Oct 7 11:32:53 > artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 Oct 7 > 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? > security_file_alloc+0x16/0x20 Oct 7 11:32:53 artemis2 kernel: > [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_unl_ioctl+0x...

...>] vfio_pci_ioctl+0x314/0xa00 [vfio_pci] > Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? kmem_cache_alloc+0x1ba/0x1d0 > Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 > Oct 7 11:32:53 artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 > Oct 7 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? security_file_alloc+0x16/0x20 > Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 > Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_unl_ioctl+0x23/...

...4/0xa00 >> [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? >> kmem_cache_alloc+0x1ba/0x1d0 Oct 7 11:32:53 artemis2 kernel: >> [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 Oct 7 11:32:53 >> artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 Oct 7 >> 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? >> security_file_alloc+0x16/0x20 Oct 7 11:32:53 artemis2 kernel: >> [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_...

...te+0x472/0x7f1 [btrfs] Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff811346ef>] ? touch_atime+0x116/0x131 Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff8112104b>] do_sync_write+0xbf/0xff Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff8114db7b>] ? fsnotify+0x1eb/0x217 Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff811e8102>] ? security_file_permission+0x2e/0x33 Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff81121436>] ? rw_verify_area+0xb0/0xcd Jul 8 11:49:40 xback2 kernel: [74920.681032] [<ffffffff811216c1>]...

...:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813b06d9>] tty_ioctl+0x289/0xbc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8119755c>] ? handle_mm_fault+0x65c/0xf50 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff812226d5>] ? fsnotify+0x265/0x350 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff811f2545>] do_vfs_ioctl+0x2e5/0x4c0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8128c42e>] ? file_has_perm+0xae/0xc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<fff...

On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 01:34:30PM +0300, ????????? ???????? wrote: > >> > > >Can anyone of you provide further hints on what

Hello, I''m seeing a lot of warnings in dmesg with a BTRFS filesystem. I''m using the 3.1 kernel, I found a patch for these warnings ( http://marc.info/?l=linux-btrfs&m=131547325515336&w=2) <http://marc.info/?l=linux-btrfs&m=131547325515336&w=2>, but that patch has already been included in 3.1. Are there any other patches I can try? I''m using