3.8-stable review patch. If anyone has any objections, please let us know.
------------------
From: "Russ Dill <[email protected]>"
commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
commit dd8004af: 'regulator: core: Log when a device causes a voltage
constraint fail', tried to print out some information about the
check consumer min/max uV fixup, however, it uses a garbage pointer
left over from list_for_each_entry leading to boot messages in the
form:
'[ 2.079890] <RANDOM ASCII>: Restricting voltage,
3735899821-4294967295uV'
Because it references regulator->dev, it could potentially read memory from
anywhere causing a panic.
This patch instead uses rdev and the updated min/max uV values.
Signed-off-by: Russ Dill <[email protected]>
Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Jonghwan Choi <[email protected]>
---
drivers/regulator/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 2785843..5a0f54a 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -200,8 +200,8 @@ static int regulator_check_consumers(struct
regulator_dev *rdev,
}
if (*min_uV > *max_uV) {
- dev_err(regulator->dev, "Restricting voltage, %u-%uuV\n",
- regulator->min_uV, regulator->max_uV);
+ rdev_err(rdev, "Restricting voltage, %u-%uuV\n",
+ *min_uV, *max_uV);
return -EINVAL;
}
--
1.7.9.5
On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> 3.8-stable review patch. If anyone has any objections, please let us know.
Who is "us"? :)
It's a bit nicer to say, "This patch looks like it should be in the
3.8-stable tree, should we apply it?"
That way, the default, if no one replies, is that the patch is not
applied (safer), not that it will be applied. I need/require that the
authors/maintainers agree that any patch they don't explicitly mark for
the stable tree, yet people think it should be, to be acknowledged by
them.
thanks,
greg k-h
On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> 3.8-stable review patch. If anyone has any objections, please let us know.
>
> ------------------
>
> From: "Russ Dill <[email protected]>"
>
> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
Wait, no, this is NOT the commit id of this patch, please don't get this
wrong.
I've dropped this from my stable mbox, if Russ feels this should go to
3.8-stable, please send me the correct git id of the patch to apply.
thanks,
greg k-h
On 04/02/2013 01:02 PM, Greg KH wrote:
> On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
>> 3.8-stable review patch. If anyone has any objections, please let us know.
>>
>> ------------------
>>
>> From: "Russ Dill <[email protected]>"
>>
>> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
>
> Wait, no, this is NOT the commit id of this patch, please don't get this
> wrong.
>
> I've dropped this from my stable mbox, if Russ feels this should go to
> 3.8-stable, please send me the correct git id of the patch to apply.
9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
This fixes a potential oops that was added in 3.8-rc4, and fixed
upstream in 3.9-rc1. I do think it belongs in stable.
Too bad I can't muck up the commit, then I'd owe you a beer. Might help
that shoulder of yours.
On Tue, Apr 02, 2013 at 01:39:06PM -0700, Russ Dill wrote:
> On 04/02/2013 01:02 PM, Greg KH wrote:
> > On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> >> 3.8-stable review patch. If anyone has any objections, please let us know.
> >>
> >> ------------------
> >>
> >> From: "Russ Dill <[email protected]>"
> >>
> >> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
> >
> > Wait, no, this is NOT the commit id of this patch, please don't get this
> > wrong.
> >
> > I've dropped this from my stable mbox, if Russ feels this should go to
> > 3.8-stable, please send me the correct git id of the patch to apply.
>
> 9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
> This fixes a potential oops that was added in 3.8-rc4, and fixed
> upstream in 3.9-rc1. I do think it belongs in stable.
Thanks, I've applied that commit now.
> Too bad I can't muck up the commit, then I'd owe you a beer. Might help
> that shoulder of yours.
Yes, that would help it out, but probably not help me catch up with
pending patches to apply :)
greg k-h
Dear all.
> > >> ------------------
> > >>
> > >> From: "Russ Dill <[email protected]>"
> > >>
> > >> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
> > >
> > > Wait, no, this is NOT the commit id of this patch, please don't get
> this
> > > wrong.
> > >
> > > I've dropped this from my stable mbox, if Russ feels this should go to
> > > 3.8-stable, please send me the correct git id of the patch to apply.
> >
> > 9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
> > This fixes a potential oops that was added in 3.8-rc4, and fixed
> > upstream in 3.9-rc1. I do think it belongs in stable.
>
-> This is my fault. I will be more careful from now on
Thanks.
Best regards.
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Greg KH
> Sent: Wednesday, April 03, 2013 5:55 AM
> To: Russ Dill
> Cc: Jonghwan Choi; [email protected]; [email protected];
> 'Mark Brown'
> Subject: Re: [PATCH 3.8-stable] regulator: core: Log when a device causes
> a voltage
>
> On Tue, Apr 02, 2013 at 01:39:06PM -0700, Russ Dill wrote:
> > On 04/02/2013 01:02 PM, Greg KH wrote:
> > > On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> > >> 3.8-stable review patch. If anyone has any objections, please let us
> know.
> > >>
> > >> ------------------
> > >>
> > >> From: "Russ Dill <[email protected]>"
> > >>
> > >> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
> > >
> > > Wait, no, this is NOT the commit id of this patch, please don't get
> this
> > > wrong.
> > >
> > > I've dropped this from my stable mbox, if Russ feels this should go to
> > > 3.8-stable, please send me the correct git id of the patch to apply.
> >
> > 9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
> > This fixes a potential oops that was added in 3.8-rc4, and fixed
> > upstream in 3.9-rc1. I do think it belongs in stable.
>
> Thanks, I've applied that commit now.
>
> > Too bad I can't muck up the commit, then I'd owe you a beer. Might help
> > that shoulder of yours.
>
> Yes, that would help it out, but probably not help me catch up with
> pending patches to apply :)
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html