public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: DAN LI <li.dan@cn.fujitsu.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] shmget/shmget01.c: cleanup and attach SHM_NORESERVE to shmflg
Date: Mon, 3 Jun 2013 16:47:40 -0400 (EDT)	[thread overview]
Message-ID: <1492205844.3281606.1370292459997.JavaMail.root@redhat.com> (raw)
In-Reply-To: <51A84F5A.9060708@cn.fujitsu.com>



----- Original Message -----
> From: "DAN LI" <li.dan@cn.fujitsu.com>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: "LTP list" <ltp-list@lists.sourceforge.net>
> Sent: Friday, 31 May, 2013 9:20:58 AM
> Subject: Re: [LTP] [PATCH] shmget/shmget01.c: cleanup and attach SHM_NORESERVE to shmflg
> 
> On 05/29/2013 06:44 PM, Jan Stancek wrote:
> > 
> > ----- Original Message -----
> >> From: "DAN LI" <li.dan@cn.fujitsu.com>
> >> To: "Jan Stancek" <jstancek@redhat.com>
> >> Cc: "LTP list" <ltp-list@lists.sourceforge.net>
> >> Sent: Wednesday, 29 May, 2013 12:25:45 PM
> >> Subject: Re: [LTP] [PATCH] shmget/shmget01.c: cleanup and attach
> >> SHM_NORESERVE to shmflg
> >>
> >> On 05/29/2013 05:18 PM, Jan Stancek wrote:
> >>>
> >>> ----- Original Message -----
> >>>> From: "DAN LI" <li.dan@cn.fujitsu.com>
> >>>> To: "LTP list" <ltp-list@lists.sourceforge.net>
> >>>> Sent: Wednesday, 29 May, 2013 10:58:47 AM
> >>>> Subject: [LTP] [PATCH] shmget/shmget01.c: cleanup and attach
> >>>> SHM_NORESERVE
> >>>> to shmflg
> >>>>
> >>>>
> >>>> 1. Remove useless comments
> >>>>
> >>>> 2. Revise code to follow ltp-code-style
> >>>>
> >>>> 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.

Regards,
Jan

> 
> And maybe, it's just what the author of this case considered since he tested
> SHM_RW(S_IRUSR | S_IWUSR) together with IPC_CREAT | IPC_EXCL.
> 
> 
> Regards,
> DAN LI
> 
> > 
> > Regards,
> > Jan
> > 
> 

------------------------------------------------------------------------------
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-03 20:47 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 [this message]
2013-06-04  7:30           ` Caspar Zhang
2013-06-04  9:46             ` DAN LI
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=1492205844.3281606.1370292459997.JavaMail.root@redhat.com \
    --to=jstancek@redhat.com \
    --cc=li.dan@cn.fujitsu.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