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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171128035105.lec6u6y4p3qwgjde@thunk.org>
Date:   Mon, 27 Nov 2017 22:51:05 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     Riccardo Schirone <sirmy15@...il.com>
Cc:     adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/3] Improve kobject handling in fs/ext4

On Tue, Nov 28, 2017 at 12:17:58AM +0100, Riccardo Schirone wrote:
> This patch tries to correctly use kobjects in fs/ext4. In particular it
> allocates kobjects/ksets dynamically, instead of statically, and improve
> error handling in case kobject_* functions fail.

I don't see the point of allocating the kobjects in question
dynamically?  There is only one of them, so why not use static
allocation?  What is "incorrect" about not doing dynamically allocated
kobjects/ksets?

Regards,

						- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ