similar to: [RESEND, PATCH v2 01/10] kobject: introduce kobject_del_and_put()

There are plenty of using kobject_del() and kobject_put() together in the kernel tree. This patch wraps these two calls in a single helper. Signed-off-by: Yangtao Li <frank.li at vivo.com> --- v3: -convert to inline helper v2: -add kobject_del_and_put() users include/linux/kobject.h | 13 +++++++++++++ lib/kobject.c | 3 +-- 2 files changed, 14 insertions(+), 2 deletions(-)

Use kobject_del_and_put() to simplify code. Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Cc: "Rafael J. Wysocki" <rafael at kernel.org> Signed-off-by: Yangtao Li <frank.li at vivo.com> --- fs/ocfs2/filecheck.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/fs/ocfs2/filecheck.c b/fs/ocfs2/filecheck.c index 1ad7106741f8..fb9cf601245b

Use kobject_del_and_put() to simplify code. Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Cc: "Rafael J. Wysocki" <rafael at kernel.org> Cc: Damien Le Moal <damien.lemoal at opensource.wdc.com> Signed-off-by: Yangtao Li <frank.li at vivo.com> --- fs/ocfs2/filecheck.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

Use kobject_del_and_put() to simplify code. Signed-off-by: Yangtao Li <frank.li at vivo.com> --- fs/ocfs2/filecheck.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/fs/ocfs2/filecheck.c b/fs/ocfs2/filecheck.c index 1ad7106741f8..fb9cf601245b 100644 --- a/fs/ocfs2/filecheck.c +++ b/fs/ocfs2/filecheck.c @@ -198,8 +198,7 @@ void ocfs2_filecheck_remove_sysfs(struct

Use kobject_del_and_put() to simplify code. Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> Cc: "Rafael J. Wysocki" <rafael at kernel.org> Cc: Damien Le Moal <damien.lemoal at opensource.wdc.com> Signed-off-by: Yangtao Li <frank.li at vivo.com> --- fs/ocfs2/filecheck.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

Here's a patch against the unstable tree that gets the code to build against Linus's current tree (2.6.24-git12). This is needed as the kobject/kset api has changed there. I tried to make the smallest changes needed, and it builds and loads successfully, but I don't have a btrfs volume anywhere (yet) to try to see if things still work properly :) Signed-off-by: Greg Kroah-Hartman

Hi filesystem maintainers, > Hard to comment on patches with this. It is only 10 patches. So send everything please. If you are interested in the entire patchset besides Damien, please let me know. I'll resend the email later to cc more people. Thx, Yangtao

Hi all, Out of consideration for minimizing disruption, I did not send the patchset to everyone. However, it seems that my consideration was unnecessary, so I CC'd everyone on the first patch. If you would like to see the entire patchset, you can access it at this address. https://lore.kernel.org/lkml/20230319092641.41917-1-frank.li at vivo.com/ Thx, Yangtao

On 3/20/23 12:34, Yangtao Li wrote: > Hi all, > > Out of consideration for minimizing disruption, I did not send the > patchset to everyone. However, it seems that my consideration was > unnecessary, so I CC'd everyone on the first patch. If you would > like to see the entire patchset, you can access it at this address. > >

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

Hi Jens, my colleague Eduardo is sporadically seeing an Oops in blk-mq while running continuous virtio_blk hot-plug/hot-unplug tests with I/O to the device within an x86_64 QEMU/KVM 2.0 Debian Wheezy VM. Please find the call trace attached and the full log here: http://paste.ubuntu.com/9691873/ The kernel image has been taken from here and is the mainline kernel from tag v3.18:

Hi Jens, my colleague Eduardo is sporadically seeing an Oops in blk-mq while running continuous virtio_blk hot-plug/hot-unplug tests with I/O to the device within an x86_64 QEMU/KVM 2.0 Debian Wheezy VM. Please find the call trace attached and the full log here: http://paste.ubuntu.com/9691873/ The kernel image has been taken from here and is the mainline kernel from tag v3.18:

The functions ttm_bo_global_init() and ttm_bo_global_release() do not receive an argument of type struct ttm_bo_global. Both take a struct drm_global_reference that contains points to a struct ttm_bo_global_ref. Renaming them reflects this. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- Documentation/gpu/drm-mm.rst | 4 ++--

It is obsoleted since Dec 2005. Signed-off-by: WANG Cong <amwang at redhat.com> --- Documentation/ABI/obsolete/o2cb | 11 ----------- Documentation/ABI/removed/o2cb | 10 ++++++++++ Documentation/feature-removal-schedule.txt | 10 ---------- fs/ocfs2/cluster/sys.c | 9 --------- 4 files changed, 10 insertions(+), 30 deletions(-) --- diff

On Sun, 17 Dec 2017 21:48:05 +0800 weiping zhang <zwp10758 at gmail.com> wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > virtio_register_device may fail before/after call

On Sun, 17 Dec 2017 21:48:05 +0800 weiping zhang <zwp10758 at gmail.com> wrote: > As mentioned at drivers/base/core.c: > /* > * NOTE: _Never_ directly free @dev after calling this function, even > * if it returned an error! Always use put_device() to give up the > * reference initialized in this function instead. > */ > virtio_register_device may fail before/after call

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

TTM uses global memory and BO for backing graphics buffers. These are represented by struct ttm_mem_global and struct ttm_bo_global. Currently, struct ttm_bo_global can only be initialized and released through struct ttm_bo_global_ref. This is a workaround for passing an instance of ttm_mem_global to the BO global initialization code. The use of struct ttm_bo_global_ref makes driver code

So far, struct ttm_bo_global_ref was the only way of initializing a struct ttm_bo_global. Providing separate initializer and release functions for struct ttm_bo_global gives drivers the option of implementing their own init and release callbacks for drm_global_references of type DRM_GLOBAL_TTM_BO. The original functions for initializing and releasing via struct ttm_bo_global_ref are wrappers