linux-kernel - Re: [PATCH 1/1] Trivial: devtmpfs.c: No need to set the task state to TASK

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 21 Sep 2011 21:06:52 +0530
From:	"kautuk.c @samsung.com" <consul.kautuk@...il.com>
To:	Greg Kroah-Hartman <gregkh@...e.de>,
	Jiri Kosina <trivial@...nel.org>, jkosina@...e.cz
Cc:	linux-kernel@...r.kernel.org,
	Kautuk Consul <consul.kautuk@...il.com>
Subject: Re: [PATCH 1/1] Trivial: devtmpfs.c: No need to set the task state to TASK_RUNNING

Hi,

Please ignore this trivial patch.
I found one more trivial change which I would like to make in this
patch, so I'll resend
this one in a separate email chain.

Thanks,
Kautuk.

On Thu, Sep 8, 2011 at 8:36 PM, Kautuk Consul <consul.kautuk@...il.com> wrote:
> I think that there should be no need to set the task state to
> TASK_RUNNING as wake_up_process will do that for us.
>
> Signed-off-by: Kautuk Consul <consul.kautuk@...il.com>
> ---
>  drivers/base/devtmpfs.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/base/devtmpfs.c b/drivers/base/devtmpfs.c
> index a4760e0..8a3f028 100644
> --- a/drivers/base/devtmpfs.c
> +++ b/drivers/base/devtmpfs.c
> @@ -416,7 +416,6 @@ static int devtmpfsd(void *p)
>                set_current_state(TASK_INTERRUPTIBLE);
>                spin_unlock(&req_lock);
>                schedule();
> -               __set_current_state(TASK_RUNNING);
>        }
>        return 0;
>  out:
> --
> 1.7.4.1
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/