Re: [PATCH] Only send SIGXFSZ when exceeding rlimits.

On Sat, 19 May 2007 17:19:35 -0700
Micah Cowan <[email protected]> wrote:

> Some users have been having problems with utilities like cp or dd
> dumping core when they try to copy a file that's too large for the
> destination filesystem (typically, > 4gb). Apparently, some defunct
> standards required SIGXFSZ to be sent in such circumstances, but SUS
> only requires/allows it for when a written file exceeds the process's
> resource limits. I'd like to limit SIGXFSZs to the bare minimum required
> by SUS.
> 
> Patch sent per http://lkml.org/lkml/2007/4/10/302
> 
> Signed-off-by: Micah Cowan <[email protected]>

Acked-by: Alan Cox <[email protected]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] Only send SIGXFSZ when exceeding rlimits.
    • From: Micah Cowan <[email protected]>

• Prev by Date: Re: 2.6.22-rc1-mm1 cifs_mount oops
• Next by Date: Re: [PATCH] fix unchecked mutex_lock_interruptible (was Re: use mutex instead of semaphore in RocketPort driver)
• Previous by thread: [PATCH] Only send SIGXFSZ when exceeding rlimits.
• Next by thread: [PATCH] Add select PHYLIB to the UCC_GETH Kconfig option
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]