[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d10f18b4-56cf-8a55-b12f-79b1163d8841@alu.unizg.hr>
Date: Thu, 9 Mar 2023 22:46:50 +0100
From: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH] block: don't embed integrity_kobj into gendisk
On 09. 03. 2023. 22:23, Thomas Weißschuh wrote:
Very well, but who then destroys the cache crated here:
security/integrity/iint.c:177-179
> 177 iint_cache =
> 178 kmem_cache_create("iint_cache", sizeof(struct integrity_iint_cache),
> 179 0, SLAB_PANIC, init_once);
I assumed that it must have been done from iint.c because iint_cache is
static?
BTW, moving check for !ktype->release to kobject_init() is great for it
might make such problems noticed in dmesg, rather than taking screenshots.
Regards,
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
The European Union
Powered by blists - more mailing lists