[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25f6950a67be079e32ad5b4139b1e89e367a91ba.camel@linux.ibm.com>
Date: Thu, 05 Oct 2023 07:47:06 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Amir Goldstein <amir73il@...il.com>,
syzbot <syzbot+b42fe626038981fb7bfa@...kaller.appspotmail.com>
Cc: hdanton@...a.com, linux-fsdevel@...r.kernel.org,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-unionfs@...r.kernel.org,
miklos@...redi.hu, mszeredi@...hat.com,
syzbot@...kalhler.appspotmail.com, syzkaller-bugs@...glegroups.com,
viro@...iv.linux.org.uk
Subject: Re: [syzbot] [integrity] [overlayfs] possible deadlock in
mnt_want_write (2)
On Thu, 2023-10-05 at 13:26 +0300, Amir Goldstein wrote:
> On Thu, Oct 5, 2023 at 12:59 PM syzbot
> <syzbot+b42fe626038981fb7bfa@...kaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot tried to test the proposed patch but the build/boot failed:
>
> My mistake. Please try again:
>
> #syz test: https://github.com/amir73il/linux ima-ovl-fix
Thanks, Amir. "mutext_init(&iint->mutex); moved, but the status
initialization lines 161-166 were dropped. They're needed by IMA-
appraisal for signature verification.
iint->ima_file_status = INTEGRITY_UNKNOWN;
iint->ima_mmap_status = INTEGRITY_UNKNOWN;
iint->ima_bprm_status = INTEGRITY_UNKNOWN;
iint->ima_read_status = INTEGRITY_UNKNOWN;
iint->ima_creds_status = INTEGRITY_UNKNOWN;
iint->evm_status = INTEGRITY_UNKNOWN;
Powered by blists - more mailing lists