From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail130.mailersend.net (mail130.mailersend.net [212.11.79.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0DE1A1F5821 for ; Sat, 13 Jun 2026 20:24:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=212.11.79.130 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781382300; cv=none; b=dlMNHYPCdkMgyg75MGAIzyh5No/NdQhZ0CyUNvH4I8FNh9+pyLYc8nlkhUImJw+TiaFgSPzyQmtIfxb2EdqDydOnYVEaUNb/VLzeZEa+68Lz+fcmcZb7DuyGIuqZ4oOtuAsJ/iEw1GjGM1tCtxXs4orAAJb/RSeQBw7Djzhq9Hc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781382300; c=relaxed/simple; bh=IsPnnkcStKwn/MBO4rst1iWYTEgBoCltqXe+kYqebD0=; h=Subject:From:To:Cc:Date:Message-ID:MIME-Version:Content-Type; b=XqcX/69P8f5JgbJP50TSJs81z4I089tM0DStxVT9Bz73VEmEOOkBvvq/KvxB6RDvjbrDDnLKHBr4xypMWGDY7I8iknng7x2Hdo78XZwFcBPXhKFFVmJjvvWCydPnOh7NLqPv7dgmguNQ01t1fQiTWkHe1l/SpIuMyKBxv2ASwKk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=hatchling.org; spf=pass smtp.mailfrom=mta.hatchling.org; dkim=pass (1024-bit key) header.d=hatchling.org header.i=@hatchling.org header.b=dxR3Hayl; dkim=pass (1024-bit key) header.d=mailersend.net header.i=@mailersend.net header.b=KBgfNxQM; arc=none smtp.client-ip=212.11.79.130 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=hatchling.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mta.hatchling.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=hatchling.org header.i=@hatchling.org header.b="dxR3Hayl"; dkim=pass (1024-bit key) header.d=mailersend.net header.i=@mailersend.net header.b="KBgfNxQM" DKIM-Signature: a=rsa-sha256; bh=5AQtSs1N99XVv55ur6IoSIyJIMJiny1kmWPnaLkE11Y=; c=relaxed/relaxed; d=hatchling.org; h=DKIM-Signature:X-Mailer-Info:Subject:From:To:Cc:Date:Received:Message-ID:X-MailerSend-RecipientID:Feedback-ID:X-MailerSend-MessageID:Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; s=mlsend2; t=1781381773; v=1; b=dxR3HaylKts9jS76jwjiwt2dpEu+AhEoYcDsbsdQGvUda2TyYBKg4ceNaGsHtmCA3CdZvDWZ eXp2riv81uhfYWP3RSivfL16hnqPhU3UBj+QoeyihiLSEe1g4mCI5BAU27aCbN+5xvMWFiNFWyy QqSvXcYdkHFnQh5aAfKo3EoU= DKIM-Signature: a=rsa-sha256; bh=5AQtSs1N99XVv55ur6IoSIyJIMJiny1kmWPnaLkE11Y=; c=relaxed/relaxed; d=mailersend.net; h=X-Mailer-Info:Subject:From:To:Cc:Date:Received:Message-ID:X-MailerSend-RecipientID:Feedback-ID:X-MailerSend-MessageID:Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; s=mlsend; t=1781381773; v=1; b=KBgfNxQMh03RN/tx8u0ub0+Q5O/ztJNS2DePTGmhVNPWX23X/O42IG6Ab3+uuZXtWNkqkUKg 7tZJAN8qdq7LjZ0L8oSMbi0wGQvXPdtL1hfzSDCPR3YDVYelxp/52dOl3fNblwQe5t5zHJKikoP jAFGRW/2WEDWTQiyYjL99hxU= X-Mailer-Info: 10.AZlZWY1xGd.AZlZWY1xGd0MTN5UzN.Abp5Wd41yalJnblxGQ2dWZy5yalJn blxmLvJ3Z.gNhJDOmFWM0ATZ2kjMhRzN0M2M5UTY1kzK0MTN5UzN.... Subject: [PATCH v2 0/2] fs/ntfs3: two fixes for large NTFS volumes From: Senjin To: ntfs3@lists.linux.dev Cc: almaz.alexandrovich@paragon-software.com, linux-kernel@vger.kernel.org Date: 13 Jun 2026 20:16:13 -0000 Received: from 10.32.22.247 by 10.132.0.99 with http; 13 Jun 2026 20:16:13 +0000 Message-ID: <6a2dba8dc035b44a31894af2@mailersend.net> X-MailerSend-RecipientID: 6a2dba8dc035b44a31894af2;6a28fa140e692a474c395a59;r9084zv9678gw63d Feedback-ID: r9084zv9678gw63d:MailerSend X-MailerSend-MessageID: 6a2dba8dd6f973735d98941f Reply-To: senjin@hatchling.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Both patches were found on a 16 TB NTFS volume with 0xFFFFFEFF total clusters, compiled with CONFIG_NTFS3_64BIT_CLUSTER=3Dy. Patch 1 is v2 of the previously submitted MFT bitmap fix, correcting a malformed hunk header in the diff. No code change from v1. Patch 2 is a new fix: sbi->maxbytes_sparse is assigned -1 in the CONFIG_NTFS3_64BIT_CLUSTER path. As a signed loff_t, -1 is the most negative value, causing vfs_setpos() to return -EINVAL for every seek on sparse or compressed files on such a volume. Sequential reads work correctly; random access does not. Fix assigns MAX_LFS_FILESIZE instead, consistent with the other two limits in the same block. Senjin (2): fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clus= ters fs/ntfs3/inode.c | 10 +++++++--- fs/ntfs3/super.c | 2 +- 2 files changed, 8 insertions(+), 4 deletions(-)