search for: debugfs

...ers can be exposed to user space, and a user-space tool (along with the logging ELF image) can parse the buffer and dump the logs. This method has the advantage that it allows the buffers to be parsed even when the logging ELF file is not available to the user. However, it has the disadvantage the debugfs entries need to remain until the driver is unloaded. The buffers are exposed via debugfs. If GSP-RM fails to initialize, then Nouveau immediately shuts down the GSP interface. This would normally also deallocate the logging buffers, thereby preventing the user from capturing the debug logs. To av...

Currently all debugfs related initialization for the DRM core happens in drm_debugfs_init(), which is called when registering the minor device. While this works fine for features such as atomic modesetting and GEM, this doesn't work at all for resources like DP MST topology managers which can potentially be created...

On Thu, 2024-10-03 at 23:48 +0200, Danilo Krummrich wrote: > > +#ifdef CONFIG_DEBUG_FS > > + /* > > + * Logging buffers in debugfs. The wrapper objects need to remain > > + * in memory until the dentry is deleted. > > + */ > > + struct dentry *dir; /* Parent dentry */ > > + struct dentry *dir_init; > > + struct dentry *dir_rm; > > + struct dentry *dir_intr; > > + struct dentry *dir_...

Sorry i don`t copy everything: TEST-MAIL1# echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722 26198604 246266859 TEST-MAIL1# echo "ls //orphan_dir:0001"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 6074335 30371669 285493670 TEST-MAIL2 ~ # echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722...

...fferent > > diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c > index 1b456fe..4cf46d8 100644 > --- a/drivers/char/virtio_console.c > +++ b/drivers/char/virtio_console.c > @@ -2215,10 +2215,8 @@ static int __init init(void) > } > > pdrvdata.debugfs_dir = debugfs_create_dir("virtio-ports", NULL); > - if (!pdrvdata.debugfs_dir) { > - pr_warning("Error %ld creating debugfs dir for virtio-ports\n", > - PTR_ERR(pdrvdata.debugfs_dir)); > - } > + if (!pdrvdata.debugfs_dir) > + pr_warning("Error creat...

...fferent > > diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c > index 1b456fe..4cf46d8 100644 > --- a/drivers/char/virtio_console.c > +++ b/drivers/char/virtio_console.c > @@ -2215,10 +2215,8 @@ static int __init init(void) > } > > pdrvdata.debugfs_dir = debugfs_create_dir("virtio-ports", NULL); > - if (!pdrvdata.debugfs_dir) { > - pr_warning("Error %ld creating debugfs dir for virtio-ports\n", > - PTR_ERR(pdrvdata.debugfs_dir)); > - } > + if (!pdrvdata.debugfs_dir) > + pr_warning("Error creat...

On Sun, Mar 12, 2023 at 4:41?PM Eli Cohen <elic at nvidia.com> wrote: > > When deleting the vdpa device, the debugfs files need to be removed so > need to remove debugfs after the device has been unregistered. > > This fixes null pointer dereference when someone deletes the device > after debugfs has been populated. > > Fixes: 294221004322 ("vdpa/mlx5: Add debugfs subtree") > Signed...

One of our users here got the following with an ext3 0.0.6b: # debugfs /dev/hda3 debugfs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 /dev/hda3: Bad magic number in super-block while opening filesystem debugfs: Does debugfs need updating? b.

...r space, and a user-space tool (along with the > logging ELF image) can parse the buffer and dump the logs. > > This method has the advantage that it allows the buffers to be parsed > even when the logging ELF file is not available to the user. However, > it has the disadvantage the debugfs entries need to remain until the > driver is unloaded. > > The buffers are exposed via debugfs. If GSP-RM fails to initialize, then > Nouveau immediately shuts down the GSP interface. This would normally > also deallocate the logging buffers, thereby preventing the user from > ca...

This is the next version of my patch series for teaching DRM how to automatically create debugfs nodes for drivers with MST topologies. This was originally intended just for nouveau, but has since been expanded to all DRM drivers. Changes since previous version: - Fix documentation error that got noticed by the kbuild bot in "drm/dp_mst: Pass entire connector to drm_dp_mst_topology_m...

...s/char/virtio_console.c > > > index 1b456fe..4cf46d8 100644 > > > --- a/drivers/char/virtio_console.c > > > +++ b/drivers/char/virtio_console.c > > > @@ -2215,10 +2215,8 @@ static int __init init(void) > > > } > > > > > > pdrvdata.debugfs_dir = debugfs_create_dir("virtio-ports", NULL); > > > - if (!pdrvdata.debugfs_dir) { > > > - pr_warning("Error %ld creating debugfs dir for virtio-ports\n", > > > - PTR_ERR(pdrvdata.debugfs_dir)); > > > - } > > > + if (!pdrvdata...

...s/char/virtio_console.c > > > index 1b456fe..4cf46d8 100644 > > > --- a/drivers/char/virtio_console.c > > > +++ b/drivers/char/virtio_console.c > > > @@ -2215,10 +2215,8 @@ static int __init init(void) > > > } > > > > > > pdrvdata.debugfs_dir = debugfs_create_dir("virtio-ports", NULL); > > > - if (!pdrvdata.debugfs_dir) { > > > - pr_warning("Error %ld creating debugfs dir for virtio-ports\n", > > > - PTR_ERR(pdrvdata.debugfs_dir)); > > > - } > > > + if (!pdrvdata...

debugfs.h protects itself from an undefined DEBUG_FS, so it is not necessary to check it in the driver code or the Makefile. The driver code had been updated for this, but the Makefile had missed the update. Link: https://lore.kernel.org/linux-next/fec68c3c-8249-7af4-5390-0495386a76f9 at infradead.org/ Fi...

...h GPU has a subdir based on its device name, so find it */ > > +???????struct drm_device *drm_dev = dev_get_drvdata(dev); > > In drm-misc-next dev_get_drvdata() returns a struct nouveau_drm. > Interestingly, > things do not blow up however. > > Instead, I noticed that your debugfs entries are created in the debugfs > root, > instead of "dri/<PCI_ID>/". Woah. > I think we shouldn't try to use the DRI debugfs directory anyway to avoid > DRM > layer dependencies in nvkm. Let's create our own nouveau one, like you did > in > earlier...

Hello friends, I am trying to learn recovering of file using debugfs. But even though i delete the file and run lsdel in debugfs it always gives me 0 deleted nodes found. Where am i making mistake?. [root at windce7 linux-2.4.32]# fdisk -l Disk /dev/hda: 40.0 GB, 40016019456 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 82252...

...can parse the buffer and dump the logs. This method has the advantage that it allows the buffers to be parsed even when the logging ELF file is not available to the user. However, it has the disadvantage the debubfs entries need to remain until the driver is unloaded. The buffers are exposed via debugfs. If GSP-RM fails to initialize, then Nouveau immediately shuts down the GSP interface. This would normally also deallocate the logging buffers, thereby preventing the user from capturing the debug logs. To avoid this, introduce the keep-gsp-logging command line parameter. If specified, and if at l...

I made a little changes in this series: 1. merge the two last patches together 2. unify the private data interface with the drm debugfs one now it should be very obvious for a new dev on how to add new files to debugfs and how to get access to the nouveau structs Karol Herbst (5): debugfs: add infrastructure to add files with other fops than only read debugfs: rename functions to indicate they are used inside drm debugf...

.../sdf failed (status 0x8). Run manually! Any ideas how to recover? Thanks, Chris ----------------------------------------------- From: "Theodore Ts'o" <tytso mit edu> To: Mike Moran <mhm austin ibm com> Cc: ext3-users redhat com Subject: Re: fixing a corrupt /dev/hdar .. debugfs assistance... Date: Mon, 28 Jul 2003 16:53:07 -0400 ________________________________ On Mon, Jul 28, 2003 at 10:42:04AM -0500, Mike Moran wrote: > Had a drive crash which a very critital inode. e2fshck > returns a stream of : > > Entry '..' in ... (#######) points to inode (2)...

...called > with a random list_head and struct nvif_log::shutdown can't be called with the > "head instance" of struct struct nvif_log. Ok, I think I got it this time. I'll post a v7 soon. > > However, I think it can happen. drm_core_init() does not fail if > > debugfs_create_dir() fails: > > > > drm_debugfs_root = debugfs_create_dir("dri", NULL); > > > > It doesn't even print a warning message. It just keeps going. So I think > > there should be some error checking somewhere. > > For DRM probably not, since...

Export initrd in debugfs when retained. As a side effect, initrd_start and initrd_end are not cleared when the initrd is retained. After this patch, one can then copy the initrd space from debugfs and pass it to kexec as the initrd, or do something else with it (maybe it was an initrd not an initramfs). Signed-off-by: M...