From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH] lib: add tst_no_corefile to avoid corefile dumping
Date: Tue, 2 Jul 2019 12:11:03 -0400 (EDT) [thread overview]
Message-ID: <1168887917.31303999.1562083863754.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2foarWKGGkV1z6RogH6wsWV__aH8K1cOvG56_yq2WBLyg@mail.gmail.com>
----- Original Message -----
> On Mon, Jul 1, 2019 at 7:01 PM Jan Stancek <jstancek@redhat.com> wrote:
>
> >
> >
> > ----- Original Message -----
> > > Signed-off-by: Li Wang <liwang@redhat.com>
> > > Cc: Jan Stancek <jstancek@redhat.com>
> > > ---
> > > include/tst_safe_macros.h | 16 ++++++++++++++++
> > > testcases/kernel/security/umip/umip_basic_test.c | 2 ++
> > > testcases/kernel/syscalls/ipc/shmat/shmat01.c | 16 +++-------------
> > > 3 files changed, 21 insertions(+), 13 deletions(-)
> > >
> > > diff --git a/include/tst_safe_macros.h b/include/tst_safe_macros.h
> > > index 53a888c80..110e2984f 100644
> > > --- a/include/tst_safe_macros.h
> > > +++ b/include/tst_safe_macros.h
> > > @@ -394,6 +394,22 @@ static inline int safe_setrlimit(const char *file,
> > const
> > > int lineno,
> > > #define SAFE_SETRLIMIT(resource, rlim) \
> > > safe_setrlimit(__FILE__, __LINE__, (resource), (rlim))
> > >
> > > +/*
> > > + * Crash is expected, avoid dumping corefile.
> > > + * 1 is a special value, that disables core-to-pipe.
> > > + * At the same time it is small enough value for
> > > + * core-to-file, so it skips creating cores as well.
> > > + */
> > > +static inline void tst_no_corefile(void)
> > > +{
> > > + struct rlimit r;
> > > +
> > > + r.rlim_cur = 1;
> > > + r.rlim_max = 1;
> > > + SAFE_SETRLIMIT(RLIMIT_CORE, &r);
> > > + tst_res(TINFO, "Avoid dumping corefile in following test");
> >
> > I'm fine with helper func. Maybe I'd print also current pid.
> > It could be little spammy if there are many children, but we could
> > address that later (if needed) with a parameter to control verbosity.
> >
>
> To add a parameter (int verbose) sounds good to me.
>
> Btw, should we add some note/comment in the
> document(test-writing-guidelines.txt)? I take a rough look but not sure
> which line is the best position for that.
How about we extend "2.2.10 Signal handlers" to "2.2.10 Signals and signal handlers"
and put a note there?
>
> --
> Regards,
> Li Wang
>
next prev parent reply other threads:[~2019-07-02 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 10:03 [LTP] [RFC PATCH] lib: add tst_no_corefile to avoid corefile dumping Li Wang
2019-07-01 11:01 ` Jan Stancek
2019-07-02 7:53 ` Li Wang
2019-07-02 16:11 ` Jan Stancek [this message]
2019-07-03 3:37 ` Li Wang
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=1168887917.31303999.1562083863754.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox