All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Lucas <clucas@altern.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Audit return codes (and handle failure correctly)
Date: Mon, 16 Jan 2006 18:33:58 +0000	[thread overview]
Message-ID: <43CBE716.3060505@altern.org> (raw)
In-Reply-To: <d9a09df00601150731g4d65ab40ya62134fbd0a8cb22@mail.gmail.com>

Alexey Dobriyan a écrit :

>On Sun, Jan 15, 2006 at 05:31:05PM +0200, Udayan Singh wrote:
>  
>
>>I am trying to understand a point mentioned in ToDo list of KJ,
>>
>>"Audit return codes (and handle failure correctly) for  " -- create_proc_*()
>>..
>>
>>I had a look at the code (in fs/proc/*, linux kernel 2.6.14).
>>
>>Clarifications that i needed :
>>
>>Is it that the wherever create_proc_* functions are being called, it needs
>>to be looked into how is it handling a failure ?
>>OR
>>Within the function(s) create_proc_*, it needs to be looked into for the
>>error codes it is receiving while it is calling other functions and handle
>>them accordingly ?
>>    
>>
>
>The former. If function can fail its return code should be checked,
>except very rare cases where you can't do anything better than panic().
>
>  
>
>>I intend to understand the above mentioned requirement and then try to do
>>it. Would appreciate information on above.
>>    
>>
>
>Be sure to grab latest kernel (2.6.16-rc1 should be out pretty soon) and
>look at latest -kj for things already done.
>  
>
Hi all,

I think you could search on :
    http://coderock.org/kj/2.6.13-rc1-kj/split/
and :
    
http://coderock.org/kj/2.6.13-rc1-kj/split/return_code-drivers_net_tokenring_olympic
could be a good start...

Have a nice day,
 

			 - Christophe (clucas@altern.org) [At home]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-01-16 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 15:31 [KJ] Audit return codes (and handle failure correctly) for Udayan Singh
2006-01-15 22:30 ` Alexey Dobriyan
2006-01-16 18:33 ` Christophe Lucas [this message]

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=43CBE716.3060505@altern.org \
    --to=clucas@altern.org \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.