[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131021231849.GL10553@sgi.com>
Date: Mon, 21 Oct 2013 18:18:49 -0500
From: Ben Myers <bpm@....com>
To: Eric Sandeen <sandeen@...deen.net>,
Dave Chinner <david@...morbit.com>
Cc: Alex Elder <elder@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
XFS FILESYSTEM <xfs@....sgi.com>,
"Geyslan G. Bem" <geyslan@...il.com>, kernel-br@...glegroups.com
Subject: Re: [PATCH] xfs: fix possible NULL dereference
Hey,
On Mon, Oct 21, 2013 at 06:12:18PM -0500, Eric Sandeen wrote:
> On 10/21/13 5:44 PM, Dave Chinner wrote:
> > On Mon, Oct 21, 2013 at 03:58:23PM -0500, Eric Sandeen wrote:
> >> On 10/21/13 1:32 PM, Geyslan G. Bem wrote:
> >>> This patch puts a 'break' in the true branch, avoiding the 'icptr->ic_next'
> >>> dereferencing.
> >>
> >> Reviewed-by: Eric Sandeen <sandeen@...hat.com>
> >
> > Actually, NACK.
>
> I felt that one coming ;)
>
> >> Hm, yeah - cmn_err(CE_PANIC, " " ); used to BUG_ON, but the newer
> >> xfs_emerg() doesn't.
> >>
> >> Dave, was that intentional?
> >
> > Of course it was. ;) xfs_emerg() is only called from the debug code
> > in xlog_verify_iclog(), xlog_verify_tail_lsn and assfail().
> >
> > In the case of assfail(), it has it's own BUG() call, so it does
> > everything just fine.
> >
> > In the case of xlog_verify_iclog() when icptr is NULL, it will
> > panic immediately after the message is printed, just like the old
> > code. i.e. this patch isn't fixing anything we need fixed.
>
> A BUG() is probably warranted, then.
I tend to agree with Eric on this point. If we want to crash, I'd rather our
intent be very clear, rather than just see a null ptr deref. ;)
Regards,
Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists