On Wed, 2006-02-08 at 12:26 +0900, Horms wrote:
I have removed the original patch from sarge-security's 2.4.27-10sarge2
as I believe that these patches are far to large for a security release.
I don't believe they have been closely examined. And we don't even
have a CVE for them. Should we add
On Fri, Oct 14, 2005 at 04:30:10PM +0900, Horms wrote:
Also this patch:
http://linux.bkbits.net:8080/linux-2.4/diffs/fs/xfs/[EMAIL
PROTECTED]|src/|src/fs|src/fs/xfs|related/fs/xfs/xfs_dinode.h|[EMAIL
PROTECTED]|hist/fs/xfs/xfs_inode.c
([XFS] Handle inode creation race) should also be
On Wed, Feb 08, 2006 at 12:26:27PM +0900, Horms wrote:
On Fri, Oct 14, 2005 at 04:30:10PM +0900, Horms wrote:
Also this patch:
http://linux.bkbits.net:8080/linux-2.4/diffs/fs/xfs/[EMAIL
PROTECTED]|src/|src/fs|src/fs/xfs|related/fs/xfs/xfs_dinode.h|[EMAIL
On Thu, Oct 13, 2005 at 02:59:30PM -0400, micah wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Horms,
I noticed that this patch is not applied to the 2.4.27 sarge1 update:
http://linux.bkbits.net:8080/linux-2.4/[EMAIL PROTECTED]
The description reads: [XFS] Add nosymlinks inode
On Thu, Oct 13, 2005 at 02:59:30PM -0400, micah wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Horms,
I noticed that this patch is not applied to the 2.4.27 sarge1 update:
http://linux.bkbits.net:8080/linux-2.4/[EMAIL PROTECTED]
The description reads: [XFS] Add nosymlinks inode
5 matches
Mail list logo