From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751106AbZHSEpR (ORCPT ); Wed, 19 Aug 2009 00:45:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751023AbZHSEpR (ORCPT ); Wed, 19 Aug 2009 00:45:17 -0400 Received: from mx2.redhat.com ([66.187.237.31]:49325 "EHLO mx2.redhat.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751000AbZHSEpQ (ORCPT ); Wed, 19 Aug 2009 00:45:16 -0400 Date: Wed, 19 Aug 2009 00:44:33 -0400 From: Amerigo Wang To: linux-kernel@vger.kernel.org Cc: esandeen@redhat.com, eteo@redhat.com, eparis@redhat.com, Amerigo Wang , linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org, sds@tycho.nsa.gov, hirofumi@mail.parknet.co.jp, viro@zeniv.linux.org.uk Message-Id: <20090819044658.5380.43869.sendpatchset@localhost.localdomain> Subject: [V5 Patch 0/2] fix file truncations when both suid and write permissions set Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrew, these two patches can replace the -mm patch "vfs-allow-file-truncations-when-both-suid-and-write-permissions-set.patch". When suid is set and the non-owner user has write permission, any writing into this file should be allowed and suid should be removed after that. However, current kernel only allows writing without truncations, when we do truncations on that file, we get EPERM. This is a bug. Steps to reproduce this bug: % ls -l rootdir/file1 -rwsrwsrwx 1 root root 3 Jun 25 15:42 rootdir/file1 % echo h > rootdir/file1 zsh: operation not permitted: rootdir/file1 % ls -l rootdir/file1 -rwsrwsrwx 1 root root 3 Jun 25 15:42 rootdir/file1 % echo h >> rootdir/file1 % ls -l rootdir/file1 -rwxrwxrwx 1 root root 5 Jun 25 16:34 rootdir/file1 This patch fixes it. Signed-off-by: WANG Cong Thanks!