From: Raghavendra K T <raghavendra.kt@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Huang, Ying" <ying.huang@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
bharata@amd.com, Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
David Hildenbrand <david@redhat.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>, Baoquan He <bhe@redhat.com>,
ilpo.jarvinen@linux.intel.com,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Fontenot Nathan <Nathan.Fontenot@amd.com>,
Wei Huang <wei.huang2@amd.com>
Subject: Re: [RFC PATCH] resource: Fix CXL node not populated issue
Date: Thu, 5 Dec 2024 11:15:08 +0530 [thread overview]
Message-ID: <557a7deb-1c38-495d-98d0-b1b2a008d99e@amd.com> (raw)
In-Reply-To: <8fdb21b6-5ea4-4be3-bfac-901ecd638897@amd.com>
On 12/4/2024 10:14 AM, Raghavendra K T wrote:
>
>
>>>>
>>>> (*) in general fixes are better than reverts, but depends on the
>>>> timing in
>>>> the release cycle the revert may be the only option.
>>>
>>> I don't think that the timing is so tight that we should not work on
>>> proper fix firstly. I'm trying to work with the reporter on this.
>>
>> I agree on this, please do.
>>
>>> BTW, the commit b4afe4183ec7 ("resource: fix region_intersects() vs
>>> add_memory_driver_managed()") fixed a security related bug. The bug
>>> weakened the protection to prevent users read/write system memory via
>>> /dev/mem. So, IMO, we need to be more careful about this.
>>
>> My point was that the regression is obvious and it needs to be fixed.
>> That's all. Revert is a last resort in this sense.
>>
>
> I agree in general to both of your comment. (i.e. since this bisected
> commit had security fix, we shall try to get better fix than a close to
> revert).
>
> I am trying to work on this, but it is a bit slow on my side.
>
I will try to get a fix that retains old bugfix and works well for me too.
Since it is reproduced only on this shared system, I will get hold of
this system next week, and work towards a fix.
Thanks and Regards
- Raghu
next prev parent reply other threads:[~2024-12-05 5:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:19 [RFC PATCH] resource: Fix CXL node not populated issue Raghavendra K T
2024-12-02 15:34 ` Andy Shevchenko
2024-12-03 6:01 ` Raghavendra K T
2024-12-03 6:26 ` Huang, Ying
2024-12-03 13:41 ` Andy Shevchenko
[not found] ` <CAAt7c_piFt2UY_OSzdhhr3yFfgMZPgcw2ogtAoVRjgDFGaG_8Q@mail.gmail.com>
2024-12-03 22:07 ` Andy Shevchenko
2024-12-04 2:07 ` Huang, Ying
2024-12-04 3:01 ` Andy Shevchenko
2024-12-04 4:44 ` Raghavendra K T
2024-12-05 5:45 ` Raghavendra K T [this message]
2024-12-04 3:55 ` Dan Williams
2024-12-04 4:41 ` Raghavendra K T
2024-12-06 7:50 ` Dan Williams
2024-12-06 8:28 ` Raghavendra K T
2024-12-11 4:44 ` Dan Williams
2024-12-11 6:40 ` Bharata B Rao
2024-12-11 8:38 ` Dan Williams
2024-12-11 16:47 ` Bharata B Rao
2024-12-12 1:02 ` Raghavendra K T
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=557a7deb-1c38-495d-98d0-b1b2a008d99e@amd.com \
--to=raghavendra.kt@amd.com \
--cc=Nathan.Fontenot@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=apopple@nvidia.com \
--cc=bharata@amd.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=vishal.l.verma@intel.com \
--cc=wei.huang2@amd.com \
--cc=ying.huang@linux.alibaba.com \
/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