| To: | Timothy Shimmin <tes@xxxxxxx> |
|---|---|
| Subject: | Re: review: block bogus bulkstat messages, last stage |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 28 Jul 2006 15:22:44 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <44C99C86.2000208@sgi.com>; from tes@sgi.com on Fri, Jul 28, 2006 at 03:11:34PM +1000 |
| References: | <20060726101537.H2118045@wobbly.melbourne.sgi.com> <44C99C86.2000208@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Jul 28, 2006 at 03:11:34PM +1000, Timothy Shimmin wrote: > 1. xfs_ialloc.c > + xfs_stack_trace(); > What's the stack trace for? > It is just to give more info after one of the 3 error msgs > beforehand? Happens in DEBUG. Okay. Yep, basically just to help figure out how the warning got triggered. If it gets triggered now, it always indicates a real problem... while before it was only possibly a problem. > Seems fine. Thanks for the review. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: review: block bogus bulkstat messages, last stage, Timothy Shimmin |
|---|---|
| Next by Date: | Re: review: fix bulkstat error detection logic, Timothy Shimmin |
| Previous by Thread: | Re: review: block bogus bulkstat messages, last stage, Timothy Shimmin |
| Next by Thread: | review: fix bulkstat error detection logic, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |