[patch] Btrfs: dereferencing free'd memory in panic message

2012-06-22 Thread Dan Carpenter
We free node and then dereference it in the panic message on the next line. I considered moving the kfree() after the panic given that panic can return under certain configurations, but in the end I decided it doesn't matter if we leak a bit after a panic. Signed-off-by: Dan Carpenter

Re: [patch] Btrfs: dereferencing free'd memory in panic message

2012-06-22 Thread Josef Bacik
On 06/22/2012 03:14 AM, Dan Carpenter wrote: We free node and then dereference it in the panic message on the next line. I considered moving the kfree() after the panic given that panic can return under certain configurations, but in the end I decided it doesn't matter if we leak a bit after a

Re: [patch] Btrfs: dereferencing free'd memory in panic message

2012-06-22 Thread Dan Carpenter
On Fri, Jun 22, 2012 at 09:09:04AM -0400, Josef Bacik wrote: On 06/22/2012 03:14 AM, Dan Carpenter wrote: We free node and then dereference it in the panic message on the next line. I considered moving the kfree() after the panic given that panic can return under certain configurations, but

Re: [patch] Btrfs: dereferencing free'd memory in panic message

2012-06-22 Thread Josef Bacik
On 06/22/2012 09:30 AM, Dan Carpenter wrote: On Fri, Jun 22, 2012 at 09:09:04AM -0400, Josef Bacik wrote: On 06/22/2012 03:14 AM, Dan Carpenter wrote: We free node and then dereference it in the panic message on the next line. I considered moving the kfree() after the panic given that panic