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: <1373595458.17876.83.camel@gandalf.local.home>
Date:	Thu, 11 Jul 2013 22:17:38 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, stable@...r.kernel.org
Subject: Re: [ 00/11] 3.4.53-stable review

On Thu, 2013-07-11 at 17:33 -0700, Greg Kroah-Hartman wrote:
> On Thu, Jul 11, 2013 at 08:24:33PM -0400, Paul Gortmaker wrote:
> > On Thu, Jul 11, 2013 at 6:11 PM, Greg Kroah-Hartman
> > <gregkh@...uxfoundation.org> wrote:
> > > This is the start of the stable review cycle for the 3.4.53 release.
> > > There are 11 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Sat Jul 13 22:04:03 UTC 2013.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > >         kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.4.53-rc1.gz
> > 
> > Just happened to notice the v3.0 in the path vs. the 3.4 version.
> > Wasn't sure that was intentional or not, so figured I'd mention it.
> 
> It's intentional, it's always been there, but I guess I could use the
> 3.x link instead, they both point to the same place.
> 

I can vouch for it always being there. I had to add a work around in my
-rt scripts to test if it was 3.0 or > 3.0, to determine what to post as
the patch set to get to an -rt kernel:

Or to build 3.0.85-rt113 directly, the following patches should be applied:

  http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.xz

  http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.85.xz

  http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/patch-3.0.85-rt113.patch.xz


Or to build 3.4.52-rt67 directly, the following patches should be applied:

  http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.4.tar.xz

  http://www.kernel.org/pub/linux/kernel/v3.x/patch-3.4.52.xz

  http://www.kernel.org/pub/linux/kernel/projects/rt/3.4/patch-3.4.52-rt67.patch.xz


Note, it's not just with stable, it's also with the main kernel tree too.

But it seems today they are the same directory. I think it wasn't like
that before the break in. Otherwise, I doubt I would have spent time on
that work around.

-- Steve




--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ