Re: [PATCH 23/23] locktorture: Check the correct variable for allocation failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 10, 2023 at 06:55:40AM -0700, Paul E. McKenney wrote:
> On Tue, Oct 10, 2023 at 01:59:21PM +0200, Frederic Weisbecker wrote:
> > From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
> > 
> > There is a typo so this checks the wrong variable.  "chains" plural vs
> > "chain" singular.  We already know that "chains" is non-zero.
> > 
> > Fixes: 7f993623e9eb ("locktorture: Add call_rcu_chains module parameter")
> > Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
> > Signed-off-by: Frederic Weisbecker <frederic@xxxxxxxxxx>
> 
> Reviewed-by: Paul E. McKenney <paulmck@xxxxxxxxxx>
> 
> A name change to increase the Hamming distance would of course also be
> good, though less urgent.  ;-)

"Hamming distance" is such a great phrase.  I'm going to use that every
time I complain about confusingly similar variable names going forward.

regards,
dan carpenter




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux