public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Thomas Backlund <tmb@mandriva.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net
Subject: Re: Linux 2.6.27.30
Date: Sun, 16 Aug 2009 21:29:14 -0700	[thread overview]
Message-ID: <20090817042914.GA20814@suse.de> (raw)
In-Reply-To: <20090817042133.GB11624@1wt.eu>

On Mon, Aug 17, 2009 at 06:21:33AM +0200, Willy Tarreau wrote:
> On Mon, Aug 17, 2009 at 02:09:32AM +0300, Thomas Backlund wrote:
> > Greg KH skrev:
> > >I'm announcing the release of the 2.6.27.30 kernel.  All users of the
> > >2.6.27 kernel series are very strongly encouraged to upgrade.
> > >
> > >I'll also be replying to this message with a copy of the patch between
> > >2.6.27.29 and 2.6.27.30
> > >
> > >The updated 2.6.27.y git tree can be found at:
> > >        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git
> > >and can be browsed at the normal kernel.org git web browser:
> > >        http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary
> > >
> > >thanks,
> > >
> > >greg k-h
> > >
> > 
> > This is broken on x86_64
> > 
> > config attached....
> > 
> > [thomas@tmb linux-2.6.27.30]$ LC_ALL=C make
> >   CHK     include/linux/version.h
> >   CHK     include/linux/utsrelease.h
> >   CALL    scripts/checksyscalls.sh
> >   CHK     include/linux/compile.h
> >   CC      fs/compat_ioctl.o
> > fs/compat_ioctl.c:1913: error: 'FS_IOC_FIEMAP' undeclared here (not in a 
> > function)
> > make[1]: *** [fs/compat_ioctl.o] Error 1
> > make: *** [fs] Error 2
> 
> indeed, fiemap was merged after 2.6.27, so the patch below was not
> appropriate for 2.6.27.x :
> 
>     [patch 16/28] compat_ioctl: hook up compat handler for FIEMAP ioctl
> 
> Greg, commit 9ac3664242f11fb38ea5029712bc77ee317fe38c should be reverted
> I think.

You are right, I'll do it in the morning and push out another .27 update
with this fix in it.

thanks,

greg k-h

  reply	other threads:[~2009-08-17  4:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16 21:35 Linux 2.6.27.30 Greg KH
2009-08-16 21:38 ` Greg KH
2009-08-16 23:09 ` Thomas Backlund
2009-08-17  4:21   ` Willy Tarreau
2009-08-17  4:29     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-17 15:33 Greg KH
2009-08-17 15:34 ` Greg KH

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=20090817042914.GA20814@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@kernel.org \
    --cc=tmb@mandriva.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox