linux-kernel - Re: [stable] Next 2.6.17-stable review cycle will be starting in about 24 hours

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]

Date:	Fri, 04 Aug 2006 12:25:08 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Neil Brown <neilb@...e.de>
Cc:	Greg KH <greg@...ah.com>, Linus Torvalds <torvalds@...l.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] Next 2.6.17-stable review cycle will be starting in
	about 24	hours

Hi Neil,

> > > > This is a heads up that the next 2.6.17-stable review cycle will be
> > > > starting in about 24 hours.  I've caught up on all pending -stable
> > > > patches that I know about and placed them in our queue, which can be
> > > > browsed online at:
> > > > 	http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=tree;f=queue-2.6.17
> > > > 
> > > > If anyone sees that this queue is missing something that they feel
> > > > should get into the next 2.6.17-stable release, please let us know at
> > > > stable@...nel.org within the next 24 hours or so.
> > > 
> > > instead of ext3-avoid-triggering-ext3_error-on-bad-nfs-file-handle.patch
> > > it makes more sense to include the revised patches from Neil:
> > > 
> > > http://comments.gmane.org/gmane.linux.kernel/430323
> > > 
> > > It seems that these are not merged upstream, but my understanding was
> > > that they were the best way to fix this. For RHEL4 we are going with
> > > these two patches. 
> > 
> > Hm, I just went with what Neil sent me for inclusion.  Neil, do you want
> > me to change the patches you sent us?
> 
> I think the patch you have is adequate for ext3.  It closes the
> important hole.  I think the extra patch for ext3 in the gmane link
> above is not entirely necessary so I wouldn't push it for stable.
> That doesn't make it a wrong choice for RHEL4 though.
> 
> The ext2 patch, on the other hand, should probably go in to stable.

this actually looks unclean to me. I thought the code duplication in
ext2 and ext3 was the price that you have to pay to avoid any layering
violation. I personally would like to see the upstream patch go into
-stable. However we don't have this upstream at the moment. So what
would you consider sending to Linus?

Regards

Marcel


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