| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 9 Jan 2024 10:18:55 +0530
From: Vimal Kumar <vimal.kumar32@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
chinmoyghosh2001@...il.com, badolevishal1116@...il.com,
mintupatel89@...il.com
Subject: Re: [PATCH v2] PM / sleep: Mechanism to find source aborting kernel
suspend transition
Apologies for delayed response.
On Sun, Dec 10, 2023 at 11:35:02AM +0100, Greg Kroah-Hartman wrote:
> On Sun, Dec 10, 2023 at 03:33:01PM +0530, Vimal Kumar wrote:
> > +#define MAX_SUSPEND_ABORT_LEN 256
>
> What does this number mean?
It was for buffer size assuming function name won't go beyond that.
We have removed this and modified to dynamic allocation in the next version.
>
> > +static DEFINE_RAW_SPINLOCK(abort_suspend_lock);
>
> Why is this a "raw" spinlock? What requires this?
We tried to use same as one used for wakeup_source. We modified to
mutex_lock in the next version.
>
> > +
> > +struct pm_abort_suspend_source {
> > + struct list_head list;
> > + char *source_triggering_abort_suspend;
> > +};
> > +static LIST_HEAD(pm_abort_suspend_list);
> > +
> > /**
> > * wakeup_source_create - Create a struct wakeup_source object.
> > * @name: Name of the new wakeup source.
> > @@ -575,6 +584,56 @@ static void wakeup_source_activate(struct wakeup_source *ws)
> > trace_wakeup_source_activate(ws->name, cec);
> > }
> >
> > +/**
> > + * abort_suspend_list_clear - Clear pm_abort_suspend_list.
> > + *
> > + * The pm_abort_suspend_list will be cleared when system PM exits.
> > + */
> > +void abort_suspend_list_clear(void)
> > +{
> > + struct pm_abort_suspend_source *info, *tmp;
> > + unsigned long flags;
> > +
> > + raw_spin_lock_irqsave(&abort_suspend_lock, flags);
> > + list_for_each_entry_safe(info, tmp, &pm_abort_suspend_list, list) {
> > + list_del(&info->list);
> > + kfree(info);
> > + }
> > + raw_spin_unlock_irqrestore(&abort_suspend_lock, flags);
> > +}
> > +EXPORT_SYMBOL_GPL(abort_suspend_list_clear);
Removed EXPORT_SYMBOL in next version and fixed the name.
> > +
> > +/**
> > + * pm_abort_suspend_source_add - Update pm_abort_suspend_list
> > + * @source_name: Wakeup_source or function aborting suspend transitions.
> > + *
> > + * Add the source name responsible for updating the abort_suspend flag in the
> > + * pm_abort_suspend_list.
> > + */
> > +static void pm_abort_suspend_source_add(const char *source_name)
> > +{
> > + struct pm_abort_suspend_source *info;
> > + unsigned long flags;
> > +
> > + info = kmalloc(sizeof(*info), GFP_KERNEL);
> > + if (!info)
> > + return;
> > +
> > + /* Initialize the list within the struct if it's not already initialized */
> > + if (list_empty(&info->list))
> > + INIT_LIST_HEAD(&info->list);
>
> How can this list head not be initialized already?
This list is internal to the structure we are defining. Check is reduntant here.
>
> > +
> > + info->source_triggering_abort_suspend = kstrdup(source_name, GFP_KERNEL);
> > + if (!info->source_triggering_abort_suspend) {
> > + kfree(info);
> > + return;
> > + }
> > +
> > + raw_spin_lock_irqsave(&abort_suspend_lock, flags);
> > + list_add_tail(&info->list, &pm_abort_suspend_list);
> > + raw_spin_unlock_irqrestore(&abort_suspend_lock, flags);
> > +}
> > +
> > /**
> > * wakeup_source_report_event - Report wakeup event using the given source.
> > * @ws: Wakeup source to report the event for.
> > @@ -590,8 +649,11 @@ static void wakeup_source_report_event(struct wakeup_source *ws, bool hard)
> > if (!ws->active)
> > wakeup_source_activate(ws);
> >
> > - if (hard)
> > + if (hard) {
> > + if (pm_suspend_target_state != PM_SUSPEND_ON)
> > + pm_abort_suspend_source_add(ws->name);
> > pm_system_wakeup();
> > + }
> > }
> >
> > /**
> > @@ -877,6 +939,7 @@ bool pm_wakeup_pending(void)
> > {
> > unsigned long flags;
> > bool ret = false;
> > + struct pm_abort_suspend_source *info;
> >
> > raw_spin_lock_irqsave(&events_lock, flags);
> > if (events_check_enabled) {
> > @@ -893,12 +956,29 @@ bool pm_wakeup_pending(void)
> > pm_print_active_wakeup_sources();
> > }
> >
> > + if (atomic_read(&pm_abort_suspend) > 0) {
> > + raw_spin_lock_irqsave(&abort_suspend_lock, flags);
> > + list_for_each_entry(info, &pm_abort_suspend_list, list) {
> > + pm_pr_dbg("wakeup source or subsystem %s aborted suspend\n",
> > + info->source_triggering_abort_suspend);
> > + }
> > + raw_spin_unlock_irqrestore(&abort_suspend_lock, flags);
> > + }
>
> After you print them all out, why not remove them from the list now?
> Why wait until later?
Yes, this can be done. We have changed it in the next version.
>
> > +
> > return ret || atomic_read(&pm_abort_suspend) > 0;
> > }
> > EXPORT_SYMBOL_GPL(pm_wakeup_pending);
> >
> > void pm_system_wakeup(void)
> > {
> > + char buf[MAX_SUSPEND_ABORT_LEN];
>
> You never actually check to ensure that you do not overflow this value,
> right? And are you _SURE_ you can put a string this big on the stack?
>
We have changed to dynamic allocation based on the required size in the next version.
> > +
> > + if (pm_suspend_target_state != PM_SUSPEND_ON) {
> > + sprintf(buf, "%ps", __builtin_return_address(0));
> > + if (strcmp(buf, "pm_wakeup_ws_event"))
>
> This is _VERY_ fragile, you are relying on a specific symbol to never
> change its name, which is not going to work in the long run, AND this
> will not work if you don't have symbols in your kernel, right?
>
As this is void function, we are depending on this symbol. We have put the
changes under debug flag in the next version.
If the symbol changes in future we need to adopt or if the pm_system_wakeup()
modified to take some input that can be used later.
> How was this tested?
>
As of now we invoked "pm_system_wakeup()" from one of the late_suspend calls
and tested this functionality which listed source_name invoking abort suspend.
> And again, why is this even needed, who will use it? What tools will
> consume it? Who will rely on it?
>
> thanks,
>
> greg k-h
Kernel developer can use this in debugging suspend failure while supporting system wide s2r.
Commit 8a537ece3d94 (PM / wakeup: Integrate mechanism to abort suspend transitions
in progress) and commit 60d4553bdc1a0 allowed to invoke pm_system_wakeup() when
wakeup_source_report_event() is called to signal a "hard" event to abort system
suspend in progress. Also, suspend can be aborted by direct call to pm_system_wakeup().
In some scenario, we have encoundered a situation where system suspend was aborted using
the above mechanism. However we faced a challenge in identifying the subsystem or module
responsible suspend failures. This will prove valuable in debugging system suspend
failures by providing details about the sources aborting suspend in progress.
Warm Regards,
Vimal Kumar
Powered by blists - more mailing lists