Re: [PATCH 3/5] exec: simplify the new ->sighand allocation

> 	- ENOMEM still can happen after de_thread(), ->sighand is not the last
> 	  object we have to allocate

As long as this is true, I think it's the incontrovertible argument there
is no reason not to simplify it.  (Not that I don't also agree with your
other reasons).


Thanks,
Roland
-
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 3/5] exec: simplify the new ->sighand allocation
  - From: Oleg Nesterov <[email protected]>

Prev by Date: Re: [PATCH 2/5] exec: simplify ->sighand switching
Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
Previous by thread: [PATCH 3/5] exec: simplify the new ->sighand allocation
Next by thread: [PATCH 1/5] exec: kill unsafe BUG_ON(sig->count) checks
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]