public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Erik Frederiksen <erik_frederiksen@pmc-sierra.com>,
	linux-kernel@vger.kernel.org
Subject: Re: IS_ERR Threshold Value
Date: Wed, 28 Jun 2006 15:39:59 -0700	[thread overview]
Message-ID: <44A3053F.9040600@zytor.com> (raw)
In-Reply-To: <20060628140825.692f31be.rdunlap@xenotime.net>

Randy.Dunlap wrote:
> On Wed, 28 Jun 2006 14:57:07 -0600 Erik Frederiksen wrote:
> 
>> from include/asm-mips/errno.h
>> #define EDQUOT      1133    /* Quota exceeded */
>>
>> I noticed that the errno value for EDQUOT on MIPS is considerably larger
>> than all others.  This can lead to a situation where functions using
>> ERR_PTR() to return error codes in pointers cannot return this error
>> code without IS_ERR() thinking that the pointer is valid.  In my case,
>> it caused an alignment exception in the XFS open call when quota has
>> been exceeded in the linux-mips 2.6.14 kernel.  I think that the XFS
>> code has changed enough that this bug isn't in newer versions, though I
>> haven't done a thorough investigation.  
>>
>> I've supplied a patch that addresses this situation by changing the
>> threshold used by IS_ERR if EMAXERRNO is defined and greater than 1000. 
>> Perhaps permanently raising the threshold value to something >1133 is
>> sufficient.
>>
>> Looking forward to your feedback.  
>>
>> Erik Frederiksen
>> Firmware Design Engineer Co-op
>> PMC-Sierra Saskatoon
> 
> Hi,
> Peter Anvin mentioned just a few days ago that this threshold value
> should be 4095 for all arches.  I think we need to get that patch
> done & submitted to Andrew for -mm.
> 

Indeed.

	-hpa

  reply	other threads:[~2006-06-28 22:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 20:57 IS_ERR Threshold Value Erik Frederiksen
2006-06-28 21:08 ` Randy.Dunlap
2006-06-28 22:39   ` H. Peter Anvin [this message]
2006-06-29 18:10   ` Ralf Baechle
2006-07-01 18:44     ` Randy.Dunlap
2006-07-01 22:23       ` H. Peter Anvin
2006-07-02 16:15         ` Ralf Baechle
2006-07-02 17:40           ` H. Peter Anvin
2006-07-02 18:22           ` Randy.Dunlap
2006-07-02 18:27         ` [PATCH] consistently use MAX_ERRNO in __syscall_return Randy.Dunlap
2006-07-03  7:39           ` Andrew Morton
2006-07-03 15:03             ` H. Peter Anvin
2006-07-03 15:42               ` Randy.Dunlap
2006-07-03 16:09                 ` H. Peter Anvin
2006-10-16 19:31     ` IS_ERR Threshold Value Andreas Mohr
2006-10-18 12:47       ` Jan Engelhardt
2006-06-28 22:41 ` Nathan Scott
2006-06-28 23:13   ` Erik Frederiksen
2006-06-28 23:22     ` Randy.Dunlap
2006-06-28 23:23     ` Nathan Scott
     [not found] <6sPiW-295-5@gated-at.bofh.it>
     [not found] ` <6sPsw-2y4-19@gated-at.bofh.it>
     [not found]   ` <6t9hu-6l6-11@gated-at.bofh.it>
     [not found]     ` <76GtI-T6-21@gated-at.bofh.it>
     [not found]       ` <77jbT-1y3-29@gated-at.bofh.it>
2006-10-18 23:29         ` Bodo Eggert

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=44A3053F.9040600@zytor.com \
    --to=hpa@zytor.com \
    --cc=erik_frederiksen@pmc-sierra.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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