linux-kernel - Re: [PATCH] serial 8250: tighten test for using backup timer

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] [day] [month] [year] [list]

Message-Id: <20080901105641.4f4d9509.akpm@linux-foundation.org>
Date:	Mon, 1 Sep 2008 10:56:41 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Will Newton" <will.newton@...il.com>
Cc:	"David Brownell" <david-b@...bell.net>,
	linux-kernel@...r.kernel.org, alex.williamson@...com
Subject: Re: [PATCH] serial 8250: tighten test for using backup timer

On Mon, 1 Sep 2008 14:36:56 +0100 "Will Newton" <will.newton@...il.com> wrote:

> On Tue, Aug 26, 2008 at 6:58 PM, Andrew Morton
> <akpm@...ux-foundation.org> wrote:
> > On Tue, 26 Aug 2008 10:45:34 -0700
> > David Brownell <david-b@...bell.net> wrote:
> >
> >> > > Also, how serious is the problem which is being fixed here?  It
> >> > > _sounds_ like it's of the "fatal for people who have that hardware"
> >> > > variety, in which case we should get this into 2.6.27 and probably
> >> > > 2.6.26.x.  Not sure about 2.5.26.x though - the patch doesn't apply
> >> > > there, but I didn't check whether this is due to functional changes.
> >> >
> >> > For users of this version of this particular UART IP it is fatal. From
> >> > looking at the git history it looks like the original patch went into
> >> > 2.6.26 so it might also affect that kernel.
> >>
> >> Second that:  serial-8250-tighten-test-for-using-backup-timer.patch
> >> (from MMOTM) in mainline sooner-not-later seems right.
> >
> > ok, if you think so...
> >
> > I still have an unanswered question out there about the init_timer()
> > handling in that area of the driver but afaict this patch didn't make any
> > of it worse than it already is.
> 
> Any update on this situation? I'd really like this patch to get into 2.6.27.

yup, I plan to include the patch in my next batch for 2.6.27.
--
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/