From: Jon Hunter <jonathanh@nvidia.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: thierry.reding@gmail.com, vdumpa@nvidia.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, baolu.lu@linux.intel.com,
jsnitsel@redhat.com, jroedel@suse.de,
linux-tegra@vger.kernel.org, iommu@lists.linux.dev,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] Failed buffer allocation in Tegra fbdev
Date: Wed, 24 Jan 2024 10:17:37 +0000 [thread overview]
Message-ID: <1eac3e8c-1bee-412b-9aae-a63ae1e54692@nvidia.com> (raw)
In-Reply-To: <pgund4coabp5pdlmwze5o2d7ogrdncktqz267yzukjcvmikudc@7svrwdci7ujl>
On 24/01/2024 09:13, Diogo Ivo wrote:
...
> I did the tracing and found that the ENOENT is coming from
> sysfs_do_create_link_sd() in the following function call chain:
>
> of_iommu_configure() -> iommu_probe_device() -> __iommu_probe_device() ->
> iommu_init_device() -> iommu_device_link() -> sysfs_add_link_to_group() ->
> sysfs_create_link_sd() -> sysfs_do_create_link_sd()
>
> The particular block that emits the error is
>
> static int sysfs_do_create_link_sd()
> {
> ...
>
> if (target_kobj->sd) {
> target = target_kobj->sd;
> kernfs_get(target);
> }
>
> if (!target)
> return -ENOENT;
>
> ...
> }
I believe that this is the same in the case that I am seeing as well.
Jon
--
nvpublic
next prev parent reply other threads:[~2024-01-24 10:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 14:33 [REGRESSION] Failed buffer allocation in Tegra fbdev diogo.ivo
2024-01-23 15:15 ` Jason Gunthorpe
2024-01-23 18:44 ` Diogo Ivo
2024-01-24 10:15 ` Jon Hunter
2024-01-24 10:30 ` Diogo Ivo
2024-01-24 10:36 ` Jon Hunter
2024-01-26 19:51 ` Jason Gunthorpe
2024-01-29 12:07 ` Diogo Ivo
2024-01-24 9:13 ` Diogo Ivo
2024-01-24 10:17 ` Jon Hunter [this message]
2024-01-24 11:46 ` Robin Murphy
2024-01-24 12:56 ` Diogo Ivo
2024-02-29 14:50 ` Jon Hunter
2024-02-29 16:46 ` Thierry Reding
2024-01-24 17:03 ` Jason Gunthorpe
2024-02-08 1:22 ` Robin Murphy
2024-02-08 2:31 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1eac3e8c-1bee-412b-9aae-a63ae1e54692@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=linux-tegra@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox