linux-kernel - Re: [PATCH] syslog: fill buffer with more than a single message for SYSLOG_ACTION

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: <20120626195511.GA2959@kroah.com>
Date:	Tue, 26 Jun 2012 12:55:11 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Kay Sievers <kay@...y.org>
Cc:	Jan Beulich <JBeulich@...e.com>, yuanhan.liu@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] syslog: fill buffer with more than a single message for
 SYSLOG_ACTION_READ

On Tue, Jun 26, 2012 at 02:34:49AM +0200, Kay Sievers wrote:
> On Tue, Jun 26, 2012 at 2:01 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> > On Mon, Jun 25, 2012 at 09:35:03PM +0200, Kay Sievers wrote:
> >> On Mon, Jun 25, 2012 at 9:20 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> >>
> >> > Ok, so I'm confused, you want me to apply this patch and then revert a
> >> > different one?  Which one, 4a77a5a06ec66ed05199b301e7c25f42f979afdc?
> >>
> >> b56a39ac conflicts and is replaced with that patch.
> >> 4a77a5a0 should stay, as it fixes an actual problem, even with the old
> >> code, I think.
> >
> > Ok, I'm even more confused now.  Maybe I just need more coffee.
> >
> > Can you list what exactly I should do here?  Should I apply this patch?
> > Revert some other patch?  Which one(s)?
> 
> Revert b56a39ac (return -EINVAL) and apply the patch from Jan. The
> problem b56a39ac solved , is replaced by other logic in Jan's patch.

Ok, now done, there's nothing else needed here, right?

thanks,

greg k-h
--
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/