All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Zummo <a.zummo@towertech.it>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "P." <mailme667@yahoo.co.uk>,
	rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	John Stultz <john.stultz@linaro.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	akpm@linux-foundation.org
Subject: Re: [PATCH resend] rtc: Fix alarm rollover when day or month is out-of-range
Date: Mon, 2 Jan 2012 14:41:38 +0100	[thread overview]
Message-ID: <20120102144138.034f5831@linux.lan.towertech.it> (raw)
In-Reply-To: <20111231003552.GB22266@elie.Belkin>

On Fri, 30 Dec 2011 18:35:52 -0600
Jonathan Nieder <jrnieder@gmail.com> wrote:

> From: Ben Hutchings <ben@decadent.org.uk>
> Date: Thu, 29 Dec 2011 16:41:56 +0100
> 
> Commit f44f7f96a20a ('RTC: Initialize kernel state from RTC')
> introduced a potential infinite loop.  If an alarm time contains a
> wildcard month and an invalid day (> 31), or a wildcard year and an
> invalid month (>= 12), the loop searching for the next matching date
> will never terminate.  Treat the invalid values as wildcards.
> 
> Fixes <http://bugs.debian.org/646429>, <http://bugs.debian.org/653331>
> 
> Reported-by: leo weppelman <leoweppelman@googlemail.com>
> Reported-by: "P. van Gaans" <mailme667@yahoo.co.uk>
> Cc: stable@vger.kernel.org
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>


 Seems reasonable, ty.


 Acked-by: Alessandro Zummo <a.zummo@towertech.it>

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


      reply	other threads:[~2012-01-02 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 23:53 P.
2011-12-31  0:35 ` [PATCH resend] rtc: Fix alarm rollover when day or month is out-of-range Jonathan Nieder
2012-01-02 13:41   ` Alessandro Zummo [this message]

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=20120102144138.034f5831@linux.lan.towertech.it \
    --to=a.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=john.stultz@linaro.org \
    --cc=jrnieder@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailme667@yahoo.co.uk \
    --cc=rtc-linux@googlegroups.com \
    /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.