public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Micah Cowan <micah@cowan.name>
To: linux-kernel@vger.kernel.org
Subject: Re: Use of SIGXFSZ outside of soft limits
Date: Tue, 10 Apr 2007 14:43:01 -0700	[thread overview]
Message-ID: <461C04E5.4090809@cowan.name> (raw)
In-Reply-To: <20070410223829.23bc3d36@the-village.bc.nu>

Alan Cox wrote:
>> [XSI] [Option Start] If the request would cause the file size to exceed 
>> the soft file size limit for the process and there is no room for any 
>> bytes to be written, the request shall fail and the implementation shall 
>> generate the SIGXFSZ signal for the thread. [Option End]
>>  >>>
> 
> This all depends which document and version you review. AIX for example
> has or had the same behaviour as Linux which comes from the Large File
> Summit and indeed our implementation was carefully tested to pass the
> test suite of the time.
> 
> SUSv3 seems to subsume the older LFS standards, and has adjusted them
> somewhat in the merging so there may well be a good case for normalizing
> our behaviour to match SUSv3. Run some tests and send patches.
> 
> Alan

Thanks very much for this response, Alan.

I kind of suspected it might be something like this. I'm relieved to 
know that the original reasons for signaling that on other cases may no 
longer apply.

I'll plan to be back with patches, then! :)

-Micah

  reply	other threads:[~2007-04-10 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 20:20 Use of SIGXFSZ outside of soft limits Micah Cowan
2007-04-10 21:38 ` Alan Cox
2007-04-10 21:43   ` Micah Cowan [this message]
2007-05-20 23:04     ` Micah Cowan

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=461C04E5.4090809@cowan.name \
    --to=micah@cowan.name \
    --cc=linux-kernel@vger.kernel.org \
    /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