All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Stefan Berger <stefanb@linux.ibm.com>,
	linux-integrity@vger.kernel.org,
	Vitaly Chikunov <vt@altlinux.org>
Subject: Re: [PATCH ima-evm-utils v4 01/17] Revert "Reset 'errno' after failure to open or access a file"
Date: Thu, 3 Nov 2022 15:32:48 +0100	[thread overview]
Message-ID: <Y2PREKTdNQhwhPEK@pevik> (raw)
In-Reply-To: <4db89eab7d21124aa7945ccf4fd150c3ee4d259c.camel@linux.ibm.com>

> On Tue, 2022-11-01 at 20:25 -0400, Stefan Berger wrote:

> > On 11/1/22 19:04, Mimi Zohar wrote:
> > > Hi Stefan,

> > > On Tue, 2022-11-01 at 17:46 -0400, Stefan Berger wrote:

> > >> On 11/1/22 16:17, Mimi Zohar wrote:
> > >>> This reverts commit acb19d1894a4a95471b8d2346cd6c3ecf3385110.

> > >> $ git show acb19d1
> > >> fatal: ambiguous argument 'acb19d1': unknown revision or path not in the working tree.

> > >> Are you reverting this from a public tree? or could you just drop this patch from your series?

> > >> Also after removing this patch from the mbox file I cannot apply these patches to my sourceforge checkout -- presumably next-testing branch:

> > >> $ git am ./v4_20221101_zohar_address_deprecated_warnings.mbx
> > >> Applying: log and reset 'errno' after failure to open non-critical files
> > >> Applying: Log and reset 'errno' on lsetxattr failure
> > >> Applying: travis: update dist=focal
> > >> Applying: Update configure.ac to address a couple of obsolete warnings
> > >> Applying: Deprecate IMA signature version 1
> > >> error: patch failed: src/libimaevm.c:684
> > >> error: src/libimaevm.c: patch does not apply
> > >> Patch failed at 0005 Deprecate IMA signature version 1
> > >> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> > >> When you have resolved this problem, run "git am --continue".
> > >> If you prefer to skip this patch, run "git am --skip" instead.
> > >> To restore the original branch and stop patching, run "git am --abort".

> > > Sorry, I should have used "--base=auto" when generating the patch set.
> > > Yes, the patch set is based on the github next-testing branch.


> > Is the github repo now the main repo and sourceforge repo is dead?

> The "next" branch in both repo's are the same.  Before posting patches,
> I verify that github Actions works.   As a result, the next-testing
> branch on github is rebased frequently.  Once a patch set is ready, the
> "next" branch in both repo's is updated.

> To answer your question the github repo is primary.
Maybe deleting everything in sourceforge and ad put single file with link to
github.com would save you work (having master, next and next-testing branches
with this file).

Kind regards,
Petr

> Mimi


  reply	other threads:[~2022-11-03 14:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 20:17 [PATCH ima-evm-utils v4 00/17] address deprecated warnings Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 01/17] Revert "Reset 'errno' after failure to open or access a file" Mimi Zohar
2022-11-01 21:46   ` Stefan Berger
2022-11-01 23:04     ` Mimi Zohar
2022-11-02  0:25       ` Stefan Berger
2022-11-03 13:54         ` Mimi Zohar
2022-11-03 14:32           ` Petr Vorel [this message]
2022-11-03 21:35             ` Mimi Zohar
2022-11-03 22:50               ` Vitaly Chikunov
2022-11-13 21:25                 ` Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 02/17] log and reset 'errno' after failure to open non-critical files Mimi Zohar
2022-11-02 21:02   ` Stefan Berger
2022-11-03  3:13     ` Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 03/17] Log and reset 'errno' on lsetxattr failure Mimi Zohar
2022-11-02 15:55   ` Stefan Berger
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 04/17] travis: update dist=focal Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 05/17] Update configure.ac to address a couple of obsolete warnings Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 06/17] Deprecate IMA signature version 1 Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 07/17] Replace the low level SHA1 calls when calculating the TPM 1.2 PCRs Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 08/17] Replace the low level HMAC calls when calculating the EVM HMAC Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 09/17] Add missing EVP_MD_CTX_free() call in calc_evm_hash() Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 10/17] Disable use of OpenSSL "engine" support Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 11/17] Fix potential use after free in read_tpm_banks() Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 12/17] Limit the file hash algorithm name length Mimi Zohar
2022-11-01 20:17 ` [PATCH ima-evm-utils v4 13/17] Missing template data size lower bounds checking Mimi Zohar
2022-11-01 20:18 ` [PATCH ima-evm-utils v4 14/17] Base sm2/sm3 test on openssl version installed Mimi Zohar
2022-11-01 21:25   ` Stefan Berger
2022-11-01 20:18 ` [PATCH ima-evm-utils v4 15/17] Compile a newer version of OpenSSL Mimi Zohar
2022-11-01 20:18 ` [PATCH ima-evm-utils v4 16/17] Build OpenSSL without engine support Mimi Zohar
2022-11-01 20:18 ` [PATCH ima-evm-utils v4 17/17] Fix d2i_x509_fp failure Mimi Zohar
2022-11-02  0:44   ` Stefan Berger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2PREKTdNQhwhPEK@pevik \
    --to=pvorel@suse.cz \
    --cc=linux-integrity@vger.kernel.org \
    --cc=stefanb@linux.ibm.com \
    --cc=vt@altlinux.org \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.