From: Chris Wedgwood <cw@f00f.org>
To: linux-kernel@vger.kernel.org
Cc: staubach@redhat.com, Andrew Morton <akpm@osdl.org>
Subject: Re: largefile-support-for-accounting.patch added to -mm tree
Date: Sat, 20 Aug 2005 19:03:06 -0700 [thread overview]
Message-ID: <20050821020306.GA17353@taniwha.stupidest.org> (raw)
In-Reply-To: <200508210034.j7L0YoH1003173@shell0.pdx.osdl.net>
On Sat, Aug 20, 2005 at 05:33:27PM -0700, akpm@osdl.org wrote:
> Another annoying problem is that once the system reaches this 2GB
> limit, then every process which exits will receive a signal,
> SIGXFSZ. This signal is generated because an attempt was made to
> write beyond the limit for the file descriptor. This signal makes
> it look like every process has exited due to a signal, when in fact,
> they have not.
Eeek.
> The solution is to add the O_LARGEFILE flag to the list of flags
> used to open the accounting file. The rest of the accounting
> support is already largefile safe.
That fixes the larger accounting file problem but it doesn't address
the fact that signals resulting writes to the accounting file are
delivered incorrectly.
We could still have issues if the accounting file as over quota for
example. Surely all accounting file writes should be insulated from
the processes involved?
parent reply other threads:[~2005-08-21 2:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200508210034.j7L0YoH1003173@shell0.pdx.osdl.net>]
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=20050821020306.GA17353@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=staubach@redhat.com \
/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
all inboxes | Powered by JetHome®