public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: DAN LI <li.dan@cn.fujitsu.com>
To: Caspar Zhang <caspar@casparzhang.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] shmget/shmget01.c: cleanup and attach SHM_NORESERVE to shmflg
Date: Tue, 04 Jun 2013 17:46:38 +0800	[thread overview]
Message-ID: <51ADB77E.7070105@cn.fujitsu.com> (raw)
In-Reply-To: <51AD9784.3080605@casparzhang.com>

On 06/04/2013 03:30 PM, Caspar Zhang wrote:
> On 06/04/2013 04:47 AM, Jan Stancek wrote:
>>>>>>> > >>>>
>>>>>>> > >>>>3. Add SHM_NORESERVE to shmflg to test
>>>>>> > >>>
>>>>>> > >>>Can you add some description why you are adding this flag?
>>>>> > >>
>>>>> > >>Actually, we are trying to complete test cases and expand
>>>>> > >>the test scope of LTP.
>>>>> > >>
>>>>> > >>So, it is just for completeness of this case.
>>>> > >
>>>> > >My concern here is:
>>>> > >So if we add this flag, we cover SHM_NORESERVE path.
>>>> > >Do we have a testcase which still covers current non-SHM_NORESERVE path?
>>> >
>>> >Hi Jan,
>>> >
>>> >Sorry for the late reply.:)
>>> >
>>> >In my opinion, SHM_NORESERVE is an independent feature of others and should
>>> >have
>>> >no effect on them, so we do not need a non-SHM_NORESERVE path.
>>> >They are like two branches of a river, one branch can do nothing on the other
>>> >one,
>>> >but if either of them goes wrong, the river will get feedback.
>> Presence of that flag has some effect, absence has different one.
>> To follow up on river metaphore, Are crocodiles in this river?
>>
>> Anyway, we cover that path in other testcases, so unless
>> someone else objects, I'm OK with adding that flag.
>>
> 
> Crocodile spotted:
> 
> in fact in this patch, SHM_NORESERVE doesn't get fully tested. from the man page:
> 
>     SHM_NORESERVE (since Linux 2.6.15)
>         [snip]When swap space is not reserved one might get SIGSEGV upon a write if no physical memory is available. [snip]
> 
> We could design such a new testcase if we really want to cover the SHM_NORESERVE branch of river (and the RESERVE branch
> as well) by set the flag and fill the memory, check the result to see if a SIGSEGV is triggered.
> 
> Thoughts?

Do you have any idea about how or what i can use to fill memory and keep away from the OOM-kill,
when trigger this SIGSEGV? :)

Regards,
DAN LI

> 
> Caspar
> 



------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2013-06-04  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:58 [LTP] [PATCH] shmget/shmget01.c: cleanup and attach SHM_NORESERVE to shmflg DAN LI
2013-05-29  9:18 ` Jan Stancek
2013-05-29 10:25   ` DAN LI
2013-05-29 10:44     ` Jan Stancek
2013-05-31  7:20       ` DAN LI
2013-06-03 20:47         ` Jan Stancek
2013-06-04  7:30           ` Caspar Zhang
2013-06-04  9:46             ` DAN LI [this message]
2013-05-29 11:27     ` Caspar Zhang
2013-05-31  7:25       ` DAN LI

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=51ADB77E.7070105@cn.fujitsu.com \
    --to=li.dan@cn.fujitsu.com \
    --cc=caspar@casparzhang.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox