Date: Tue, 10 Jan 2017 15:58:29 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Liljestrand Hans <ishkamiel@...il.com> Cc: "Reshetova, Elena" <elena.reshetova@...el.com>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Greg KH <gregkh@...uxfoundation.org>, Kees Cook <keescook@...omium.org>, "will.deacon@....com" <will.deacon@....com>, Boqun Feng <boqun.feng@...il.com>, David Windsor <dwindsor@...il.com>, "aik@...abs.ru" <aik@...abs.ru>, "david@...son.dropbear.id.au" <david@...son.dropbear.id.au> Subject: Re: Conversion from atomic_t to refcount_t: summary of issues On Tue, Dec 20, 2016 at 05:20:08PM +0200, Liljestrand Hans wrote: > fs/inode.c:813 find_inode_fast > > This seems to be doing a search for freed up objects that are then > reused, maybe. Not sure if we can guarantee the refcount is 0, nor if it > would be appropriate to use refcount_set even if we could? This one is actually quite difficult. I'll try and poke at it some.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.