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: <CAPXgP11rkrk5LBYswPf_3nOD2e2oYnvWgbFb81NYgjta67Dj3w@mail.gmail.com>
Date:	Mon, 25 Jun 2012 21:35:03 +0200
From:	Kay Sievers <kay@...y.org>
To:	Greg KH <gregkh@...uxfoundation.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 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.

> Kay, do you agree?

Yes, seems, we need to restore the old behaviour, even when it's worse
than the current one. The stuff SUSE does here really doesn't sound
right, but it's history done long ago, and we an not change that.

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