From: Mark Lord <lkml@rtr.ca>
To: Adrian Bunk <bunk@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>
Subject: Re: 2.6.25-rc7-git5: Reported regressions from 2.6.24
Date: Mon, 31 Mar 2008 15:24:10 -0400 [thread overview]
Message-ID: <47F13A5A.7040305@rtr.ca> (raw)
In-Reply-To: <20080331191733.GB23259@cs181133002.pp.htv.fi>
Adrian Bunk wrote:
> On Mon, Mar 31, 2008 at 01:48:15PM -0400, Mark Lord wrote:
>> Rafael,
>>
>> Add this one to the list?
>
>
> That's not a regression from 2.6.24
..
2.6.24 does not flood my syslog with those messages.
2.6.25-rc* does. Looks like a regression.
The original bug was a hidden regression in 2.6.23,
which nobody bothered to identify until now.
Just because some code "gets away with" a regression
for a kernel or two, doesn't mean that regression shouldn't be fixed.
Cheers
>
>
>> * * * * *
>>
>> Subject: + driver-core-fix-uevent-action-string-regression.patch added to -mm tree
>> From: akpm
>> To: mm-commits
>> Date: 28/03/08 07:51 PM
>>
>> The patch titled
>> driver core: fix uevent action-string regression
>> has been added to the -mm tree. Its filename is
>> driver-core-fix-uevent-action-string-regression.patch
>> ...
>>
>> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>>
>> ------------------------------------------------------
>> Subject: driver core: fix uevent action-string regression
>> From: Mark Lord <lkml@rtr.ca>
>>
>> On boot, syslog is flooded with "uevent: unsupported action-string;" messages.
>> ..
>> Mar 28 14:43:29 shrimp kernel: tty ptyqd: uevent: unsupported
>> action-string; this will be ignored in a future kernel version
>> Mar 28 14:43:29 shrimp kernel: tty ptyqe: uevent: unsupported
>> action-string; this will be ignored in a future kernel version
>> Mar 28 14:43:29 shrimp kernel: tty ptyqf: uevent: unsupported
>> action-string; this will be ignored in a future kernel version
>> Mar 28 14:43:29 shrimp kernel: tty ptyr0: uevent: unsupported
>> action-string; this will be ignored in a future kernel version
>>
>>
>> These messages are a regression compared with 2.6.24, which did not flood the
>> syslog with them.
>>
>> The actual underlying problem was introduced in 2.6.23, when somebody made the
>> string parsing no longer accept nul-terminated strings as a valid input to
>> store_uevent().
>>
>> Eg. "add\0" was valid prior to 2.6.23, where the code regressed to require
>> "add" without the '\0'.
>>
>> This patch fixes the 2.6.23 / 2.6.24 regressions, by having the code once
>> again tolerate the trailing '\0', if present.
>>
>> According to GregKH, this mainly affects older Ubuntu systems, such as the one
>> I have here that requires this fix.
>>
>> Signed-off-by: Mark Lord <mlord@pobox.com>
>> Cc: Greg KH <greg@kroah.com>
>> Cc: Kay Sievers <kay.sievers@vrfy.org>
>> Cc: <stable@kernel.org>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>> ---
>>
>> lib/kobject_uevent.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff -puN lib/kobject_uevent.c~driver-core-fix-uevent-action-string-regression lib/kobject_uevent.c
>> --- a/lib/kobject_uevent.c~driver-core-fix-uevent-action-string-regression
>> +++ a/lib/kobject_uevent.c
>> @@ -59,7 +59,7 @@ int kobject_action_type(const char *buf,
>> enum kobject_action action;
>> int ret = -EINVAL;
>>
>> - if (count && buf[count-1] == '\n')
>> + if (count && (buf[count-1] == '\n' || buf[count-1] == '\0'))
>> count--;
>>
>> if (!count)
>> _
>>
>> Patches currently in -mm which might be from lkml@rtr.ca are
>>
>> driver-core-fix-uevent-action-string-regression.patch
>
> cu
> Adrian
>
next prev parent reply other threads:[~2008-03-31 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 0:28 2.6.25-rc7-git5: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-03-31 17:48 ` Mark Lord
2008-03-31 19:17 ` Adrian Bunk
2008-03-31 19:24 ` Mark Lord [this message]
2008-03-31 19:35 ` Adrian Bunk
2008-03-31 20:31 ` Rafael J. Wysocki
2008-04-02 21:00 ` Bongani Hlope
2008-04-02 21:57 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F13A5A.7040305@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.