From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] syscalls/acct02: Fix failures with nearly full FS
Date: Mon, 15 Jul 2019 13:19:51 +0200 [thread overview]
Message-ID: <20190715111950.GA12926@rei> (raw)
In-Reply-To: <5D2C35B6.6080606@cn.fujitsu.com>
Hi!
> I met the same problem on last week when I ran acct02 on nearly full
> FS. Since kernel/acct.c has defined the RESUME(4) and SUSPEND(2)
> macro, 4.1 is enough. And I think we can leave a simple comment in
> here for why the limit is 4.1(even though the commit message has the
> reason).
I guess that short comment would help there, if it's OK I will add it
before I push the patch.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-07-15 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 14:15 [LTP] [PATCH 0/2] Fix acct failures on nearly full FS Cyril Hrubis
2019-07-12 14:15 ` [LTP] [PATCH 1/2] safe_macros: Add SAFE_STATFS() Cyril Hrubis
2019-07-12 14:15 ` [LTP] [PATCH 2/2] syscalls/acct02: Fix failures with nearly full FS Cyril Hrubis
2019-07-15 8:13 ` Yang Xu
2019-07-15 11:19 ` Cyril Hrubis [this message]
2019-07-15 11:27 ` Yang Xu
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=20190715111950.GA12926@rei \
--to=chrubis@suse.cz \
--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