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: <20180528125257.bppijdymfnsr3yqz@quack2.suse.cz>
Date:   Mon, 28 May 2018 14:52:57 +0200
From:   Jan Kara <jack@...e.cz>
To:     Amir Goldstein <amir73il@...il.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>, Jan Kara <jack@...e.cz>,
        Sasha Levin <alexander.levin@...rosoft.com>
Subject: Re: [PATCH 4.16 231/272] fanotify: Avoid lost events due to ENOMEM
 for unlimited queues

On Mon 28-05-18 15:39:04, Amir Goldstein wrote:
> On Mon, May 28, 2018 at 1:04 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > 4.16-stable review patch.  If anyone has any objections, please let me know.
> >
> 
> I do not have objections for applying this patch to stable, but AFAIK
> it is a correctness patch that doesn't fix any bug and it was mainly added
> as a prerequisite to memcg accounting of event allocations, which is not
> yet merged and not destined for stable.
> 
> Jan? do you agree with my statements above?

Yes, you are correct. The problem this patch tries to fix is theoretical in
nature at this point. However my feeling is stable tree has got rather
benevolent in accepting patches in last months and Greg wishes it stays that
way so I'm objecting only to patches I know introduce regressions at this
point.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ