Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1396304

Re: [PATCH] debugobjects: insulate non-fixup logic related to static obj from fixup callbacks

Show all headers | View raw

On Sat, May 07, 2016 at 10:26:28AM +0200, Thomas Gleixner wrote:
> On Sat, 7 May 2016, changbin.du@intel.com wrote:
> 
> Can you please fix your mail client. Every mail you send has:
> 
> Cc: .....
>     "Du, Changbin" <changbin.du@intel.com>,
>     Du
> 
> And that stray 'Du' is just broken.
> 
> > At last, I have a concern about the fixups that can it change the
> > object which is in incorrect state on fixup? Because the 'addr' may
> > not point to any valid object if a non-static object is not tracked.
> > Then Change such object can overwrite someone's memory and cause
> > unexpected behaviour. For example, the timer_fixup_activate bind
> > timer to function stub_timer.
> 
> Well, you have the choice of:
> 
>  1) Leave the object uninitialized and watch the resulting explosion
> 
>  2) Assume that the pointer is a valid object and initialize it     
> 
> The latter has been chosen as the lesser of two evils.
> 
> >  		raw_spin_unlock_irqrestore(&db->lock, flags);
> >  		/*
> > -		 * Maybe the object is static.  Let the type specific
> > +		 * Maybe the object is static. Let the type specific
> >  		 * code decide what to do.
> 
> Instead of doing white space changes you really want to explain the logic
> here.
> 
> >  		 */
> > -		if (debug_object_fixup(descr->fixup_assert_init, addr,
> > -				       ODEBUG_STATE_NOTAVAILABLE))
> > +		if (descr->is_static_object && descr->is_static_object(addr)) {
> > +			/* Make sure that it is tracked in the object tracker */
> > +			debug_object_init(addr, descr);
> > +		} else {
> >  			debug_print_object(&o, "assert_init");
> > +			debug_object_fixup(descr->fixup_assert_init, addr,
> > +					   ODEBUG_STATE_NOTAVAILABLE);
> > +		}
> >  		return;
> >  	}
> 
> Other than the missing comment this looks good.

The transformation to the RCU code looks fine.  So given changes so
that Thomas is good with the overall change, I am good with it from an
RCU perspective.

							Thanx, Paul

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH] debugobjects: insulate non-fixup logic related to static obj from fixup callbacks changbin.du@intel.com - 2016-05-07 01:30 +0200
  Re: [PATCH] debugobjects: insulate non-fixup logic related to static  obj from fixup callbacks kbuild test robot <lkp@intel.com> - 2016-05-07 02:20 +0200
  Re: [PATCH] debugobjects: insulate non-fixup logic related to static  obj from fixup callbacks Thomas Gleixner <tglx@linutronix.de> - 2016-05-07 10:30 +0200
    Re: [PATCH] debugobjects: insulate non-fixup logic related to static  obj from fixup callbacks "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-05-07 14:50 +0200
    RE: [PATCH] debugobjects: insulate non-fixup logic related to  static obj from fixup callbacks "Du, Changbin" <changbin.du@intel.com> - 2016-05-08 09:50 +0200
      RE: [PATCH] debugobjects: insulate non-fixup logic related to static  obj from fixup callbacks Thomas Gleixner <tglx@linutronix.de> - 2016-05-08 18:20 +0200
        RE: [PATCH] debugobjects: insulate non-fixup logic related to  static obj from fixup callbacks "Du, Changbin" <changbin.du@intel.com> - 2016-05-09 05:10 +0200
        [PATCH v2] debugobjects: insulate non-fixup logic related to static obj from fixup callbacks changbin.du@intel.com - 2016-05-09 09:20 +0200

csiph-web