From owner-freebsd-security@freebsd.org Wed Jul 3 14:41:51 2019 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94F3215D5D92 for ; Wed, 3 Jul 2019 14:41:51 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9E1276668 for ; Wed, 3 Jul 2019 14:41:50 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f49.google.com with SMTP id r185so5346586iod.6 for ; Wed, 03 Jul 2019 07:41:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ohRv5PZ6le0qWR72ys6dx/2QM8+Uu8T+Yp3XoAG1BYo=; b=t+6AoELVrlSkeUYEYWsY0wL2FfeiwywhXYAFW39fdfLqPEfSWn1sl9FVWl+dK9u9mS 8t7qixanj96iK2K4tG9FDGLDE7FF6dV2gwOKnkxP+9DnE7YHTQHry+OknZLNlxM1TosH 1Jbf5FM3qL+qIiuL3HIXwNRdwrRZV3MqO1F8bnHfLvwGS38jWqRkXvBFh4tV0lBIgRqi n/jL0Rvzo/6TbTbH9HH979cIxUHMCiYdx2Nsgdt6HcpFChuizE6s1/EJmWOAiXCQkwuF LjwF9lAM3y5nFpp1+r5ZhuGujnTnOYyKlT+rw+vaiK2MOT3Yck6HxSM/nFTplHTbVi1S 6ZcQ== X-Gm-Message-State: APjAAAVVQJc6jZo1FtbojWoa+ZgMMJdbB9lh7zB9MMhMgWo6dzA1Hesx 6Wv/S/p32earwQqcIJPtRjxKAoEP9AsaGb9vG8M= X-Google-Smtp-Source: APXvYqyGTlcK7llhLc1ly33InhQM7MT8Ckn6p2wgwItIGWAAB34ZHqBoOpq5KWhQ5/GWT8ynijRF3ZM172FnqPaDubw= X-Received: by 2002:a6b:b497:: with SMTP id d145mr26544099iof.17.1562164904080; Wed, 03 Jul 2019 07:41:44 -0700 (PDT) MIME-Version: 1.0 References: <20190703004924.8A5411A7D5@freefall.freebsd.org> In-Reply-To: From: Ed Maste Date: Wed, 3 Jul 2019 06:41:11 -0400 Message-ID: Subject: Re: FreeBSD Security Advisory FreeBSD-SA-19:10.ufs To: Doug Hardie Cc: freebsd-security@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: C9E1276668 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.49 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-security@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[49.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.91)[-0.914,0]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; IP_SCORE(-2.67)[ip: (-7.48), ipnet: 209.85.128.0/17(-3.45), asn: 15169(-2.37), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jul 2019 14:41:51 -0000 On Wed, 3 Jul 2019 at 06:05, Doug Hardie wrote: > > > Afterwards, reboot the system and run: > > > > # fsck -t ufs -f -p -T ufs:-z > > > > to clean up your existing filesystems. > > After rebooting the system I get: > > master# fsck -t ufs -f -p -T ufs:-z > /dev/ada0p2: NO WRITE ACCESS > /dev/ada0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > Is this expected result or is there a problem here? Thanks for reporting this - it looks like some more detail will need to be added to the SA. The fsck needs to be run without the filesystem being mounted read-write, most likely in single user mode. I brought a test system down to single user mode, remounted / as read-only, and ran the fsck command as follows: # shutdown now ... Enter full pathname of shell or RETURN for /bin/sh: # mount -u -o ro / # fsck -t ufs -f -p -T ufs:-z /dev/ufsid/5bf225f5889c157d: 28576 files, 304757 used, 27570235 free (899 frags, 3446167 blocks, 0.0% fragmentation) # exit