search for: exit_signals

The default path is /var/run/tftpd-hpa.pid, which can be overridden by the newly introduced -P option. On normal termination (SIGTERM or SIGINT) the pid file is automatically removed. Moved setting the umask later, right before entering the select loop, so that it does not affect the permissions of the pid file. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 38

Hi, This is my current patch queue. The patches are independent, AFAIK, so feel free to cherry-pick or reject them independently. The bottom one was needed for a successful build here; the top one contains all the modifications you requested on IRC, and more. Meanwhile I hit one of the four stray TABs in tftpd.c, and decided to get rid of them. Comments welcome. --- Ferenc Wagner (5):

Hello I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a lot of disk access, deletions and symlinks creations... Maybe It is due to the kernel version. Could you please inform me if must upgrade to a more recent kernel ? Thanks a lot the kernel logs are : in errors logs Oct 18 17:31:16 tadorne kernel: Assertion failure in journal_revoke_Rb5884a32() at revoke.c:307:

On Fri, May 5, 2023 at 6:40?AM Nicolas Dichtel <nicolas.dichtel at 6wind.com> wrote: > > Is this an intended behavior? > This breaks some of our scripts. It doesn't just break your scripts (which counts as a regression), I think it's really wrong. The worker threads should show up as threads of the thing that started them, not as processes. So they should show up in

On 5/5/23 1:22 PM, Linus Torvalds wrote: > On Fri, May 5, 2023 at 6:40?AM Nicolas Dichtel > <nicolas.dichtel at 6wind.com> wrote: >> >> Is this an intended behavior? >> This breaks some of our scripts. > > It doesn't just break your scripts (which counts as a regression), I > think it's really wrong. > > The worker threads should show up as

...;ffffffff8103a2d9>] ? console_unlock+0x1b6/0x1e9 [34736.266568] [<ffffffff8105c46c>] ? __cond_resched+0x1d/0x26 [34736.266571] [<ffffffff81358b79>] ? _cond_resched+0x11/0x1b [34736.266575] [<ffffffff813583d0>] ? down_read+0x9/0x19 [34736.266579] [<ffffffff81048681>] ? exit_signals+0x1c/0x115 [34736.266583] [<ffffffff8103cbe0>] ? do_exit+0x10f/0x7a9 [34736.266587] [<ffffffff81078b95>] ? arch_local_irq_save+0x11/0x17 [34736.266592] [<ffffffff8135950c>] ? _raw_spin_lock_irqsave+0x9/0x25 [34736.266595] [<ffffffff8103b09a>] ? kmsg_dump+0x52/0xdc [34736...

The following patches made over Linus's tree fix the 2 bugs: 1. vhost worker task shows up as a process forked from the parent that did VHOST_SET_OWNER ioctl instead of a process under root/kthreadd. This was causing breaking scripts. 2. vhost_tasks didn't disable or add support for freeze requests. The following patches fix these issues by making the vhost_task task a thread under the

...5.8.0-rc5-00191-g086f86c033f9 #53 Hardware name: Gigabyte Technology Co., Ltd. X299 AORUS Gaming 3 Pro/X299 AORUS Gaming 3 Pro-CF, BIOS F5d 11/28/2019 Call Trace: dump_stack (/home/kas/linux/torvalds/lib/dump_stack.c:120) ___might_sleep.cold (/home/kas/linux/torvalds/kernel/sched/core.c:6900) exit_signals (/home/kas/linux/torvalds/include/linux/percpu-rwsem.h:51 /home/kas/linux/torvalds/include/linux/cgroup-defs.h:733 /home/kas/linux/torvalds/kernel/signal.c:2828) do_exit (/home/kas/linux/torvalds/kernel/exit.c:764) ? ksys_ioctl (/home/kas/linux/torvalds/fs/ioctl.c:48 /home/kas/linux/torvalds/fs/i...

On Sun, May 21, 2023 at 09:51:24PM -0500, Mike Christie wrote: > When switching from kthreads to vhost_tasks two bugs were added: > 1. The vhost worker tasks's now show up as processes so scripts doing ps > or ps a would not incorrectly detect the vhost task as another process. > 2. kthreads disabled freeze by setting PF_NOFREEZE, but vhost tasks's > didn't disable or

...000000b90 0000000000000000 [ 315.186614] Call Trace: [ 315.186618] [<ffffffff814d56bf>] dump_stack+0x68/0x92 [ 315.186622] [<ffffffff810d5e6a>] ___might_sleep+0x3bd/0x3c9 [ 315.186625] [<ffffffff810d5fd1>] __might_sleep+0x15b/0x167 [ 315.186630] [<ffffffff810ac4c1>] exit_signals+0x7a/0x34f [ 315.186633] [<ffffffff810ac447>] ? get_signal+0xd9b/0xd9b [ 315.186636] [<ffffffff811aee21>] ? irq_work_queue+0x101/0x11c [ 315.186640] [<ffffffff8111f0ac>] ? debug_show_all_locks+0x226/0x226 [ 315.186645] [<ffffffff81096357>] do_exit+0x34d/0x1b4e [ 315...

...0 > [ 315.186614] Call Trace: > [ 315.186618] [<ffffffff814d56bf>] dump_stack+0x68/0x92 > [ 315.186622] [<ffffffff810d5e6a>] ___might_sleep+0x3bd/0x3c9 > [ 315.186625] [<ffffffff810d5fd1>] __might_sleep+0x15b/0x167 > [ 315.186630] [<ffffffff810ac4c1>] exit_signals+0x7a/0x34f > [ 315.186633] [<ffffffff810ac447>] ? get_signal+0xd9b/0xd9b > [ 315.186636] [<ffffffff811aee21>] ? irq_work_queue+0x101/0x11c > [ 315.186640] [<ffffffff8111f0ac>] ? debug_show_all_locks+0x226/0x226 > [ 315.186645] [<ffffffff81096357>] do_exit...

...0 > [ 315.186614] Call Trace: > [ 315.186618] [<ffffffff814d56bf>] dump_stack+0x68/0x92 > [ 315.186622] [<ffffffff810d5e6a>] ___might_sleep+0x3bd/0x3c9 > [ 315.186625] [<ffffffff810d5fd1>] __might_sleep+0x15b/0x167 > [ 315.186630] [<ffffffff810ac4c1>] exit_signals+0x7a/0x34f > [ 315.186633] [<ffffffff810ac447>] ? get_signal+0xd9b/0xd9b > [ 315.186636] [<ffffffff811aee21>] ? irq_work_queue+0x101/0x11c > [ 315.186640] [<ffffffff8111f0ac>] ? debug_show_all_locks+0x226/0x226 > [ 315.186645] [<ffffffff81096357>] do_exit...

...6f86c033f9 #53 > Hardware name: Gigabyte Technology Co., Ltd. X299 AORUS Gaming 3 Pro/X299 AORUS Gaming 3 Pro-CF, BIOS F5d 11/28/2019 > Call Trace: > dump_stack (/home/kas/linux/torvalds/lib/dump_stack.c:120) > ___might_sleep.cold (/home/kas/linux/torvalds/kernel/sched/core.c:6900) > exit_signals (/home/kas/linux/torvalds/include/linux/percpu-rwsem.h:51 /home/kas/linux/torvalds/include/linux/cgroup-defs.h:733 /home/kas/linux/torvalds/kernel/signal.c:2828) > do_exit (/home/kas/linux/torvalds/kernel/exit.c:764) > ? ksys_ioctl (/home/kas/linux/torvalds/fs/ioctl.c:48 /home/kas/linux/torva...

Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() family of modifiers to handle broken userspace Xorg modesetting and Mesa drivers. Tested with Xorg 1.20 modesetting driver, weston at c46c70dac84a4b3030cd05b380f9f410536690fc, gnome & KDE wayland desktops from Ubuntu 18.04, and sway 1.5 Signed-off-by: James Jones <jajones at nvidia.com> --- drivers/gpu/drm/nouveau/nouveau_display.c | 26

...000000b90 0000000000000000 [ 319.372911] Call Trace: [ 319.372915] [<ffffffff814d69b0>] dump_stack+0x68/0x92 [ 319.372919] [<ffffffff810d6165>] ___might_sleep+0x3bd/0x3c9 [ 319.372922] [<ffffffff810d62cc>] __might_sleep+0x15b/0x167 [ 319.372927] [<ffffffff810ac7bf>] exit_signals+0x7a/0x34f [ 319.372931] [<ffffffff810ac745>] ? get_signal+0xd9b/0xd9b [ 319.372934] [<ffffffff811af758>] ? irq_work_queue+0x101/0x11c [ 319.372938] [<ffffffff8111f405>] ? debug_show_all_locks+0x226/0x226 [ 319.372943] [<ffffffff81096655>] do_exit+0x34d/0x1b4e [ 319...

When switching from kthreads to vhost_tasks two bugs were added: 1. The vhost worker tasks's now show up as processes so scripts doing ps or ps a would not incorrectly detect the vhost task as another process. 2. kthreads disabled freeze by setting PF_NOFREEZE, but vhost tasks's didn't disable or add support for them. To fix both bugs, this switches the vhost task to be thread in the

Hi Mike, sorry, but somehow I can't understand this patch... I'll try to read it with a fresh head on Weekend, but for example, On 06/01, Mike Christie wrote: > > static int vhost_task_fn(void *data) > { > struct vhost_task *vtsk = data; > - int ret; > + bool dead = false; > + > + for (;;) { > + bool did_work; > + > + /* mb paired w/

...me: init [1266874889.610522] Pid: 1, comm: init Tainted: G D W 3.5.0upstream-00242-g3992c03 #1 [1266874889.610522] Call Trace: [1266874889.610522] [<c108d7cc>] __might_sleep+0xdc/0x110 [1266874889.610522] [<c150c067>] down_read+0x17/0x30 [1266874889.610522] [<c107814a>] exit_signals+0x1a/0x140 [1266874889.610522] [<c106c0e1>] do_exit+0x91/0x8b0 [1266874889.610522] [<c150b1d7>] ? printk+0x38/0x3a [1266874889.610522] [<c150ead0>] oops_end+0x90/0xd0 [1266874889.610522] [<c103656f>] die+0x4f/0x70 [1266874889.610522] [<c150e556>] do_trap+0x96/0xd0...

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be migrated with current compaction algorithm which supports only LRU pages. In the end, compaction cannot

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be migrated with current compaction algorithm which supports only LRU pages. In the end, compaction cannot