linux-kernel - Re: [PATCH] devtmpfs: Calling delete

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFRkauAzR=BqJGrMzN0i-tvi5mcQvyB9Kihk0YvxMpk=SWGvFA@mail.gmail.com>
Date:	Wed, 4 Dec 2013 14:44:14 +0800
From:	Axel Lin <axel.lin@...ics.com>
To:	Rob Landley <rob@...dley.net>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Kay Sievers <kay.sievers@...y.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] devtmpfs: Calling delete_path() only when necessary

2013/12/4 Rob Landley <rob@...dley.net>:
> On 11/16/2013 02:15:23 AM, Axel Lin wrote:
>>
>> The deleted variable is always 1 in current code.
>> Initialize deleted variable to be 0, so delete_path() will be called only
>> when
>> necessary.
>>
>> Signed-off-by: Axel Lin <axel.lin@...ics.com>
>
>
> I'm not seeing this in linux-next, or a reply on the web archive. Assuming
> nobody's objected to this, you might want to forward it to
> trivial@...nel.org.
>
> That said, you could describe what it _does_ a little more?

I was expecting Greg to pick up this patch.

I thought the description is pretty clear.
What the patch does is changing the init value of deleted variable to 0.
The intention of this change is to avoid unnecessary delete_path() call.

Hi Greg,
Would you pick up this patch?
If a re-send or a v2 is required, please just let me know.

Thanks,
Axel
--
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/