search for: exit_files

Displaying 10 results from an estimated 10 matches for "exit_files".

Did you mean: edit_files
2002 Apr 22
3
[PATCH] open files in kjounald
...patch ASAP - thank you very much. Regards, Phil diff -ru linux/fs/jbd/journal.c linux.ori/fs/jbd/journal.c --- linux/fs/jbd/journal.c Mon Apr 22 06:29:16 2002 +++ linux.ori/fs/jbd/journal.c Mon Apr 22 06:28:54 2002 @@ -204,7 +204,6 @@ lock_kernel(); daemonize(); - exit_files(current); spin_lock_irq(&current->sigmask_lock); sigfillset(&current->blocked); recalc_sigpending(current);
2023 Jun 06
2
[CFT][PATCH v3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
...alls vhost_task_create() to > >> create the task_struct which runs the vhost_worker() function which handles > >> the work->fns. > >> 3. If userspace now does a SIGKILL or just exits without doing a close() on > >> /dev/vhost-$something, then when thread0 does exit_files() that will do the > >> fput that does vhost-$something's file_operations->release. > > > > So, at least in this simple case vhost_worker() can just exit after SIGKILL, > > and thread0 can flush the outstanding commands when it calls vhost_dev_flush() > > rat...
2002 Apr 22
1
Re: [PATCH] open files in kjounald (2)
...patch ASAP - thank you very much. Regards, Phil diff -ru linux/fs/jbd/journal.c linux.ori/fs/jbd/journal.c --- linux.ori/fs/jbd/journal.c Mon Apr 22 06:28:54 2002 +++ linux/fs/jbd/journal.c Mon Apr 22 06:29:16 2002 @@ -204,7 +204,6 @@ lock_kernel(); daemonize(); + exit_files(current); spin_lock_irq(&current->sigmask_lock); sigfillset(&current->blocked); recalc_sigpending(current);
2023 Jun 05
1
[CFT][PATCH v3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
...something. 2. thread0 does VHOST_SET_OWNER ioctl. This calls vhost_task_create() to create the task_struct which runs the vhost_worker() function which handles the work->fns. 3. If userspace now does a SIGKILL or just exits without doing a close() on /dev/vhost-$something, then when thread0 does exit_files() that will do the fput that does vhost-$something's file_operations->release.
2023 Jun 06
1
[CFT][PATCH v3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
...0 does VHOST_SET_OWNER ioctl. This calls vhost_task_create() to > create the task_struct which runs the vhost_worker() function which handles > the work->fns. > 3. If userspace now does a SIGKILL or just exits without doing a close() on > /dev/vhost-$something, then when thread0 does exit_files() that will do the > fput that does vhost-$something's file_operations->release. So, at least in this simple case vhost_worker() can just exit after SIGKILL, and thread0 can flush the outstanding commands when it calls vhost_dev_flush() rather than wait for vhost_worker(). Right? not t...
2023 Jun 06
1
[CFT][PATCH v3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
..._OWNER ioctl. This calls vhost_task_create() to >> create the task_struct which runs the vhost_worker() function which handles >> the work->fns. >> 3. If userspace now does a SIGKILL or just exits without doing a close() on >> /dev/vhost-$something, then when thread0 does exit_files() that will do the >> fput that does vhost-$something's file_operations->release. > > So, at least in this simple case vhost_worker() can just exit after SIGKILL, > and thread0 can flush the outstanding commands when it calls vhost_dev_flush() > rather than wait for vhost_...
2011 Nov 18
3
[PATCH] vhost-net: Acquire device lock when releasing device
...5985] [<ffffffff818d4f18>] vhost_net_release+0x48/0x7f [ 2025.657247] [<ffffffff811416e3>] fput+0x11e/0x1dc [ 2025.658091] [<ffffffff8113f1ec>] filp_close+0x6e/0x79 [ 2025.658964] [<ffffffff81089ed7>] put_files_struct+0xcc/0x196 [ 2025.659971] [<ffffffff8108a034>] exit_files+0x46/0x4f [ 2025.660865] [<ffffffff8108a716>] do_exit+0x264/0x75c [ 2025.662201] [<ffffffff8113f490>] ? fsnotify_modify+0x60/0x68 [ 2025.663260] [<ffffffff81bbdbca>] ? sysret_check+0x2e/0x69 [ 2025.664269] [<ffffffff8108acc1>] do_group_exit+0x83/0xb1 [ 2025.665448] [&lt...
2011 Nov 18
3
[PATCH] vhost-net: Acquire device lock when releasing device
...5985] [<ffffffff818d4f18>] vhost_net_release+0x48/0x7f [ 2025.657247] [<ffffffff811416e3>] fput+0x11e/0x1dc [ 2025.658091] [<ffffffff8113f1ec>] filp_close+0x6e/0x79 [ 2025.658964] [<ffffffff81089ed7>] put_files_struct+0xcc/0x196 [ 2025.659971] [<ffffffff8108a034>] exit_files+0x46/0x4f [ 2025.660865] [<ffffffff8108a716>] do_exit+0x264/0x75c [ 2025.662201] [<ffffffff8113f490>] ? fsnotify_modify+0x60/0x68 [ 2025.663260] [<ffffffff81bbdbca>] ? sysret_check+0x2e/0x69 [ 2025.664269] [<ffffffff8108acc1>] do_group_exit+0x83/0xb1 [ 2025.665448] [&lt...
2023 May 24
1
[PATCH 3/3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
On 05/23, Eric W. Biederman wrote: > > I want to point out that we need to consider not just SIGKILL, but > SIGABRT that causes a coredump, as well as the process peforming > an ordinary exit(2). All of which will cause get_signal to return > SIGKILL in this context. Yes, but probably SIGABRT/exit doesn't really differ from SIGKILL wrt vhost_worker(). > It is probably not
2023 May 22
1
[PATCH 3/3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
...; But who will call the release function / vhost_task_stop() and when this > > will happen after this thread gets SIGKILL ? > > When we get a SIGKILL, the thread that owns the device/vhost_task will > also exit since it's the same thread group and it does: > > do_exit -> exit_files -> put_files_struct -> close_files -> fput Ah. thanks. I confused CLONE_FS in vhost_task_create() with CLONE_FILES. > > Also. Suppose that vhost_worker() dequeues SIGKILL and clears TIF_SIGPENDING. > > > > SIGSTOP, PTRACE_INTERRUPT, freezer can come and set TIF_SIGPENDI...