lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 29 Dec 2014 22:02:56 -0600
From:	Dave Kleikamp <dave.kleikamp@...cle.com>
To:	tytso@....edu, nick <xerofoify@...il.com>,
	jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: Remove TO DO in jfs_xtree.c

On 12/29/2014 09:48 PM, tytso@....edu wrote:
> On Mon, Dec 29, 2014 at 04:13:37PM -0600, Dave Kleikamp wrote:
>> On 12/27/2014 06:58 PM, nick wrote:
>>> Greetings Dave,
>>> I am wondering why there is a TO DO above this code:
>>>         * ToDo:  tlocks should be on doubly-linked list, so we can
>>>         * quickly remove it and add it to the end.
>>
>> I'm sure the idea was to avoid the for loop needed to find the previous
>> entry in the linked list. A doubly-linked list makes it much simpler to
>> remove an item from an arbitrary position in the list.
> 
> Hi Dave,
> 
> Just in case you weren't aware, Nick has been banned from the LKML
> list for being a troll.

Thanks, Ted. Now I remember some earlier threads. Forgot it was the same
person. Just figured him for a novice looking for something to contribute.

Thanks,
Shaggy
--
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