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: <CAM_iQpUUD5v9LHDjpjR0tM4NkQehDYqoZ7UGDSmXvqf3uiEHjQ@mail.gmail.com>
Date:	Wed, 13 Aug 2014 17:16:35 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	David Rientjes <rientjes@...gle.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>, Tejun Heo <tj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Patch v2] freezer: check OOM kill while being frozen

On Wed, Aug 13, 2014 at 2:26 AM, Michal Hocko <mhocko@...e.cz> wrote:
> On Tue 12-08-14 17:53:33, Cong Wang wrote:
>> On Tue, Aug 12, 2014 at 4:44 AM, Michal Hocko <mhocko@...e.cz> wrote:
> [...]
>> >> @@ -147,12 +156,6 @@ void __thaw_task(struct task_struct *p)
>> >>  {
>> >>       unsigned long flags;
>> >>
>> >> -     /*
>> >> -      * Clear freezing and kick @p if FROZEN.  Clearing is guaranteed to
>> >> -      * be visible to @p as waking up implies wmb.  Waking up inside
>> >> -      * freezer_lock also prevents wakeups from leaking outside
>> >> -      * refrigerator.
>> >> -      */
>> >
>> > This is an unrelated change.
>> >
>>
>> It is, because as I explained, __thaw_task() doesn't do what this comment
>> says therefore needs this patch. Or you prefer to make it a separated patch?
>
> It is outdated since a3201227f803. I would do it in a separate patch but
> maybe just mention that the above commit has changed the implementation.
>

OK, I will split this patch.
--
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/

Powered by blists - more mailing lists