On 02/20, Andrew Morton wrote:
>
> On Wed, 20 Feb 2013 23:32:26 +0100
> Oleg Nesterov wrote:
>
> > Andrew, could you take it? We will make more fixes on top.
>
> Did that, but the timing and somewhat tentative nature of the changes
> makes me think "3.10-rc1".
Oh, yes, I will sleep much better if
On Wed, 20 Feb 2013 23:32:26 +0100
Oleg Nesterov wrote:
> On 02/19, Mandeep Singh Baines wrote:
> >
> > For the whole series:
> >
> > Tested-by: Mandeep Singh Baines
>
> Oh, thanks a lot Mandeep.
>
> I tried to test it too, seems to work.
>
> Andrew, could you take it? We will make more fixes
On 02/19, Mandeep Singh Baines wrote:
>
> For the whole series:
>
> Tested-by: Mandeep Singh Baines
Oh, thanks a lot Mandeep.
I tried to test it too, seems to work.
Andrew, could you take it? We will make more fixes on top.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe li
On Sun, Feb 17, 2013 at 11:18 AM, Oleg Nesterov wrote:
> Hello.
>
> These problems are really annoying. I reported and tried to fix
> them in 2008 (see http://marc.info/?l=linux-kernel&m=121665710711931)
> but nobody was interested.
>
> Since then I had a lot of (to some degree contradictory) bug
On 02/17, Oleg Nesterov wrote:
>
> On 02/17, Linus Torvalds wrote:
> >
> > SIGKILL really is very very special. Having it kill a
> > coredump in progress sounds fine to me.
>
> Great.
Forgot to mention just in case...
We could probably make a simpler patch. do_coredump() can ignore
all signals ex
On 02/17, Linus Torvalds wrote:
>
> On Sun, Feb 17, 2013 at 11:18 AM, Oleg Nesterov wrote:
> >
> > Linus, et al, could you please ack/nack the intent? Of course I will
> > appreciate if you can review the code, but what I am actually worried
> > about is the user-visible change: the coredumping be
On Sun, Feb 17, 2013 at 11:18 AM, Oleg Nesterov wrote:
>
> Linus, et al, could you please ack/nack the intent? Of course I will
> appreciate if you can review the code, but what I am actually worried
> about is the user-visible change: the coredumping becomes killable but
> only by the _explicit_
Hello.
These problems are really annoying. I reported and tried to fix
them in 2008 (see http://marc.info/?l=linux-kernel&m=121665710711931)
but nobody was interested.
Since then I had a lot of (to some degree contradictory) bug reports:
we do not want the interrupted coredumps (this is what the
8 matches
Mail list logo