From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/kill11: add a check between hard limit and MIN_RLIMIT_CORE
Date: Thu, 13 Feb 2020 18:11:59 +0800 [thread overview]
Message-ID: <00adce02-dc66-b766-bf27-7d45922d7a94@cn.fujitsu.com> (raw)
In-Reply-To: <22de5707-18fb-f552-caed-aff4e9922c6d@cn.fujitsu.com>
on 2020/02/13 16:41, Yang Xu wrote:
>
>
> on 2020/02/13 16:35, Jan Stancek wrote:
>>
>>
>> ----- Original Message -----
>>>> This looks OK, but could we also raise the limit when possible?
>>>>
>>> Of course. Your way is more wise.
>>> But I also want to change this size of MIN_RLIMIT_CORE.
>>> ? From ulimit manpage, I know in posix mode "-c" used 512-byte block. I
>>> doubt whether we can change MIN_RLIMIT_CORE(512 *1024), so this case
>>> can also pass in unbuntu(default environment).
>>> What do you think about this?
>>
>> I don't see problem with that, we only check for correct signal.
>> Though it probably should be separate patch. Can you re-post
>> both as 2 patch series?
Hi Jan
Since abort01 has the same issue, I will send a patch series as you
advise, and then cleanup kill11 when I have free time.
Best Regargd
Yang Xu
> Hi Jan
> ?I perfer to cleanup this case to use new API and also include this two
> points.
>
> Best Regard
> Yang Xu
>>
>>
>>
>
>
>
prev parent reply other threads:[~2020-02-13 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 5:44 [LTP] [PATCH] syscalls/kill11: add a check between hard limit and MIN_RLIMIT_CORE Yang Xu
2020-02-12 6:11 ` Xiao Yang
2020-02-12 6:41 ` Yang Xu
2020-02-12 13:32 ` Jan Stancek
2020-02-13 1:43 ` Yang Xu
2020-02-13 8:35 ` Jan Stancek
2020-02-13 8:41 ` Yang Xu
2020-02-13 10:11 ` Yang Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00adce02-dc66-b766-bf27-7d45922d7a94@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.