Re: [PATCH printk-rework 07/14] printk: use atomic64_t for devkmsg_user.seq

2021-02-19 Thread Petr Mladek
On Thu 2021-02-18 09:18:10, John Ogness wrote: > @user->seq is indirectly protected by @logbuf_lock. Once @logbuf_lock > is removed, @user->seq will be no longer safe from an atomicity point > of view. > > In preparation for the removal of @logbuf_lock, change it to > atomic64_t to provide this sa

[PATCH printk-rework 07/14] printk: use atomic64_t for devkmsg_user.seq

2021-02-18 Thread John Ogness
@user->seq is indirectly protected by @logbuf_lock. Once @logbuf_lock is removed, @user->seq will be no longer safe from an atomicity point of view. In preparation for the removal of @logbuf_lock, change it to atomic64_t to provide this safety. Signed-off-by: John Ogness --- kernel/printk/print