Applied, thanks!
Sergey Bugaev, le lun. 26 juin 2023 02:11:34 +0300, a ecrit:
> The code already ignores proc_mark_important failing with EPERM; do the
> same for opening /servers/startup and startup_request_notification. All
> of these calls will fail for unprivileged mounts.
>
> Also plug a por
The code already ignores proc_mark_important failing with EPERM; do the
same for opening /servers/startup and startup_request_notification. All
of these calls will fail for unprivileged mounts.
Also plug a port leak: we want to deallocate the "init" port whether the
RPC succeeds or not.
---
libdi
I applied, thanks!
Just one thing: I moved the functions so as to get the code in the
execution order: fsys_startup, then fsys_init, then
arrange_shutdown_notification, and S_startup_dosync before
trivfs_goaway.
Samuel
Damien Zammit, le sam. 01 août 2020 15:05:38 +1000, a ecrit:
> +static void
> +device_shutdown (void)
> +{
> + struct block_data *bd = block_head;
> +
> + while (bd)
> +{
> + device_close((void *)bd);
> + bd = bd->next;
> +}
> + rump_sys_reboot (0, NULL);
> +}
Did you check th
Samuel Thibault, le dim. 02 août 2020 23:16:22 +0200, a ecrit:
> Damien Zammit, le sam. 01 août 2020 15:09:57 +1000, a ecrit:
> > I figured out why it was hanging on reboot:
> > netdde was frozen because pci-arbiter was not working
> > with my setup that used x86 method of pci access for rumpdisk.
Hello,
Damien Zammit, le sam. 01 août 2020 15:09:57 +1000, a ecrit:
> I figured out why it was hanging on reboot:
> netdde was frozen because pci-arbiter was not working
> with my setup that used x86 method of pci access for rumpdisk.
>
> When I removed the translators from /dev/netdde and /serve
Hi,
I figured out why it was hanging on reboot:
netdde was frozen because pci-arbiter was not working
with my setup that used x86 method of pci access for rumpdisk.
When I removed the translators from /dev/netdde and /servers/bus/pci,
reboot-hurd rebooted cleanly with this patch.
Damien
---
libmachdev/Makefile | 4 +-
libmachdev/ds_routines.c | 10 +++
libmachdev/machdev-device_emul.h | 1 +
libmachdev/machdev.h | 1 +
libmachdev/trivfs_server.c | 116 ++-
libmachdev/trivfs_server.h | 33 +
r
Damien Zammit, le mar. 28 juil. 2020 20:08:36 +1000, a ecrit:
> +++ b/libmachdev/startup.c
> --- a/libmachdev/trivfs_server.c
As mentioned previously, please keep it inside trivfs_server.c. The
bootstrap process is already hairy by happening in different
translators, let's not add complexity by ha
NB: Reboot still hangs on diskfs_S_startup_dosync() even though that
times out and then rumpdisk shuts down cleanly.
---
libmachdev/Makefile | 6 +--
libmachdev/ds_routines.c | 10
libmachdev/machdev-device_emul.h | 1 +
libmachdev/machdev.h | 1 +
lib
Damien Zammit, le dim. 26 juil. 2020 17:37:21 +1000, a ecrit:
> @@ -183,7 +185,16 @@ S_i386_io_perm_create (mach_port_t master_port,
>return i386_io_perm_create (_hurd_device_master, from, to, io_perm);
> }
>
> -/* This is fraud */
> +kern_return_t
> +trivfs_S_fsys_init (struct trivfs_contro
Damien Zammit, le dim. 26 juil. 2020 17:37:21 +1000, a ecrit:
> This patch almost provides shutdown notification for rumpdisk,
> but fails at getproc() which returns 0, I struggle to figure out why.
> +void
> +arrange_shutdown_notification ()
> +{
> + error_t err;
> +
This patch almost provides shutdown notification for rumpdisk,
but fails at getproc() which returns 0, I struggle to figure out why.
Currently:
Hurd server bootstrap: ext2fs[part:2:device:/dev/wd0] ...
WARNING: machdev not registered for shutdown
---
libmachdev/Makefile | 6
Damien Zammit, le sam. 25 juil. 2020 16:51:50 +1000, a ecrit:
> -SRCS = ds_routines.c trivfs_server.c \
> - deviceServer.c notifyServer.c mach_i386Server.c
> +SRCS = ds_routines.c trivfs_server.c startup_notifyServer.c \
> + deviceServer.c notifyServer.c mach_i386Server.c startup.c
> s
current boot in runlevel 6.
> Stopping deferred execution scheduler: atd.
> Asking all remaining processes to terminate...
This is a concern with the reboot command, not with the reboot-hurd
command. Only the latter is concerned with the startup notification
thing. Try to debug with reboot-hurd
This still does not work. I get a freeze on reboot command:
root@zamhurd:~# reboot
INIT: Switching to runlevel: 6
INIT: Sending processes configured via /etc/inittab the TERM signal
root@zamhurd:~#
Broadcast message from root@zamhurd (console) (Sun Jul 25 16:32:28 1999):
The system is going down
Funny to see a *.patch (and later on a *.diff) file being classified as
a security threat ...
On Wed, 2015-07-08 at 15:55 +0200, nore...@kth.se wrote:
> ###
>
> F-Secure Anti-Virus for Microsoft Exchange has processed the message
> sent by 'bug-hurd-bounces
Justus Winter, le Tue 20 Jan 2015 20:30:59 +0100, a écrit :
> * utils/rpctrace.c (new_receiver_info): Fix handling of old
> notification port.
Ack, thanks!
> ---
> utils/rpctrace.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/utils/rpctrace
Justus Winter, le Tue 20 Jan 2015 20:30:58 +0100, a écrit :
> This fixes a deallocation of an invalid port notably seen on system
> shutdown.
Ack, thanks!
> * console/display.c (free_modreqs): Handle errors of
> `mach_port_request_notification' and check whether the old
> n
This fixes a deallocation of an invalid port notably seen on system
shutdown.
* console/display.c (free_modreqs): Handle errors of
`mach_port_request_notification' and check whether the old
notification port was valid.
(do_mach_notify_msg_accepted): Likewise.
(display_notice_filechange): Lik
* utils/rpctrace.c (new_receiver_info): Fix handling of old
notification port.
---
utils/rpctrace.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/utils/rpctrace.c b/utils/rpctrace.c
index 62d3c87..48daa07 100644
--- a/utils/rpctrace.c
+++ b/utils/rpctrace.c
@@ -404,7
Justus Winter, le Wed 10 Dec 2014 17:21:56 +0100, a écrit :
> Now that we do not use sequence numbers anymore, we can simply use
> libports notification server functions.
>
> * libpager/Makefile (SRCS): Drop `no-senders.c', and `notify-stubs.c'.
> (OBJS): Drop `noti
Now that we do not use sequence numbers anymore, we can simply use
libports notification server functions.
* libpager/Makefile (SRCS): Drop `no-senders.c', and `notify-stubs.c'.
(OBJS): Drop `notifyServer.o'.
* libpager/demuxer.c (pager_demuxer): Use libports server functions.
--- /dev/null
+++ b/hurd/process_notify.defs
@@ -0,0 +1,21 @@
+/* XXX */
+
+subsystem process_notify 24500;
+
+#include
+
+#ifdef PROCESS_NOTIFY_IMPORTS
+PROCESS_NOTIFY_IMPORTS
+#endif
+
+/* For maximum robustness, the server must not wait for the client to
+ receive the notification message. This is
XXX
---
libhurdnotify/Makefile | 28 ++
libhurdnotify/notify.c | 251
libhurdnotify/notify.h | 73 ++
3 files changed, 352 insertions(+)
create mode 100644 libhurdnotify/Makefile
create mode 100644 libhurdnotify/notify.c
crea
Applied them both, finally!
Thanks,
Samuel
XXX
---
libnotify/Makefile | 28 ++
libnotify/notify.c | 152
libnotify/notify.h | 50 +
3 files changed, 230 insertions(+)
create mode 100644 libnotify/Makefile
create mode 100644 libnotify/notify.c
create mode 1
HURD_IHASH_ITERATE_ITEMS macro
I'd also like to propose this as an alternative to the
HURD_IHASH_ITERATE macro that only exposes the value, not the
key. This one gives one both the key and the value. The implementation
is also a lot less scary.
[PATCH 4/7] libnotify: add a general notification library
--- /dev/null
+++ b/hurd/process_notify.defs
@@ -0,0 +1,21 @@
+/* XXX */
+
+subsystem process_notify 24500;
+
+#include
+
+#ifdef PROCESS_NOTIFY_IMPORTS
+PROCESS_NOTIFY_IMPORTS
+#endif
+
+/* For maximum robustness, the server must not wait for the client to
+ receive the notification message. This is
declaration.
* libpager/data-request.c (_pager_seqnos_memory_object_data_request): Take
pager's `notify_on_evict' member into account when calling
memory_object_data_supply.
* libpager/data-return.c (_pager_do_write_request): Handle user notification
on page flush.
* libpager/page
Hi,
All the notification RPCs (in notify.defs) are simple routines, i.e.,
the client (the kernel) doesn't expect the replies.
Then what is the meaning of the return values of their server code?
Take the function below as an example (it is in proc/notify.c).
If the task port becomes a
Thomas Bushnell BSG wrote:
If you want to serve that file, you'll be writing a trivfs translator
for it.
I'm sorry, I don't understand you.
The translator associated to the device file is actually written with
libtrivfs.
Good grief, I can't keep track of what you are talking a
On Wed, 2008-08-27 at 03:38 +0200, Da Zheng wrote:
> Thomas Bushnell BSG wrote:
> > On Wed, 2008-08-27 at 01:56 +0200, Da Zheng wrote:
> >
> >>> Yes, but the point here is that *you* are opening that file and
> >>> expecting something to happen. I thought you were writing the program
> >>> whic
Thomas Bushnell BSG wrote:
On Wed, 2008-08-27 at 01:56 +0200, Da Zheng wrote:
Yes, but the point here is that *you* are opening that file and
expecting something to happen. I thought you were writing the program
which would *serve* that file.
I know it's a bit confusing. Then what
On Wed, 2008-08-27 at 01:56 +0200, Da Zheng wrote:
> > Yes, but the point here is that *you* are opening that file and
> > expecting something to happen. I thought you were writing the program
> > which would *serve* that file.
> >
> I know it's a bit confusing. Then what should I do?
If you w
Thomas Bushnell BSG wrote:
On Tue, 2008-08-26 at 13:09 +0200, Da Zheng wrote:
The purpose of the translator is to help other programs get the port to
the device, so I suggested if it was OK that file_name_lookup() returns
the port to the device directly.
antrik said it was quite confusing fo
On Tue, 2008-08-26 at 13:09 +0200, Da Zheng wrote:
> The purpose of the translator is to help other programs get the port to
> the device, so I suggested if it was OK that file_name_lookup() returns
> the port to the device directly.
> antrik said it was quite confusing for him because file_name_
Thomas Bushnell BSG wrote:
The device file is created by a translator to help other user programs
to open the device.
For example, we can create a device file /dev/eth0 with the translator.
When the user program calls file_name_lookup() on the file and
device_open() as I do in the code, I actua
On Mon, 2008-08-25 at 19:31 +0200, Da Zheng wrote:
> I don't want to destroy the port. I just want to check if all ports have
> already been destroyed before the goaway routine is called.
To check, you use the counting routines provided.
> The device file is created by a translator to help other
Thomas Bushnell BSG wrote:
On Mon, 2008-08-25 at 13:20 +0200, Da Zheng wrote:
Yes, these ports have the receive rights.
They are used for the user program, and I want to make sure they have
all been destroyed before the translator exits, so the translator knows
all user programs connected t
On Mon, 2008-08-25 at 13:20 +0200, Da Zheng wrote:
> Yes, these ports have the receive rights.
> They are used for the user program, and I want to make sure they have
> all been destroyed before the translator exits, so the translator knows
> all user programs connected to it have all exited and
can exit
without causing any problems.
I think every translator does it. For example, pfinet checks
"ports_count_class (socketport_class) != 0" in its trivfs_goaway(). If
the count of socket port class isn't 0, pfinet doesn't exit.
When all user programs exit, the no-senders
ll all be destroyed.
> Assume that I create a port for the user programs and give its send
> right to them.
> After ports_create_port() and several ports_get_right() are called, the
> reference count of the port is 2.
Yes.
> When all user programs exit, the no-senders notific
turns.
Maybe I haven't made it clear enough. We are thinking about it in a
different angle. My point is how to make sure the port will be destroyed
in no-sender notification.
As I said above, I have to make sure all ports created for the user
program have been destroyed before the translato
On Sat, 2008-08-23 at 09:36 -0700, Thomas Bushnell BSG wrote:
> So you have two ports. When the one going to the user is destroyed, you
> need to tell the device not to send any more packets.
>
> And we have a way to do that: by calling device_set_filter, and clearing
> out the port there. The d
On Sat, 2008-08-23 at 13:25 +0200, Da Zheng wrote:
> I have to make sure every ports has been destroyed so when the
> translator exits, it can check if there are still users.
Huh? When the translator exits, all the ports are going to be destroyed
anyway.
> OK, maybe I should make the things mor
ct.
When the user program exits, the port for it can be destroyed by
no-sender notification,
You are thinking "how can we destroy the port", which is the wrong
question. But yes, when the user has had this event, the port can be
destroyed.
I have to make sure every ports
wo ways to destroy the port_info object:
> either to call ports_port_deref() and then ports_destroy_right() explicitly,
> or to call ports_port_deref() and then wait until no_senders
> notification is generated.
NO, NO, NO. The reference count is poor-man's-gc. It's garbage
col
. So when we do a ports_destroy_right, first we
blow away the receive right, which causes the kernel to nuke all the
outstanding send rights and turn them into MACH_PORT_NULL. Then we
account for their loss by doing a ports_port_deref, if there were any
send rights. (Notice that the no-senders
rn them into MACH_PORT_NULL. Then we
account for their loss by doing a ports_port_deref, if there were any
send rights. (Notice that the no-senders notification we have
outstanding is going to be cancelled when we nuke the receive right.)
The only reason that ports_port_deref might not immediate
ut note that destroying the receive right is quickly going to
result in the reference count for the port going to zero, and the
consequent destruction of the port_info structure. But that step will
happen later, when the last no-senders notification comes in.
ports_destroy_right decrease the ref
only when its
> reference count is 0), right?
Yes, but note that destroying the receive right is quickly going to
result in the reference count for the port going to zero, and the
consequent destruction of the port_info structure. But that step will
happen later, when the last no-senders notif
n its
reference count is 0), right?
I realize now that I really need to use libports very carefully.
Another question is about the notification of no senders.
From the mach manual, I see there are two situations where no-senders
notification is generated.
1. "If notify is not null, and the recei
Title: PayPal
Protect Your Account InfoMake sure you never provide your password to fraudulent websites.
PayPal will never ask you to enter your password in an email.
For more information on protecting yourself from fraud, please review our Security Tips at https://www.paypal.com/us/security
employees.
Notification of Possible Account Fraud
As part of our security measures, we regularly screen activity in the PayPal system. We recently noticed the following
issue on your account:
We have determined that different computers have logged onto your PayPal
Title: Untitled Document
Dear User,
As part of our security measures, we regularly screen activity in the
PayPal system. We recently noticed the following issue on your account:
We would like to ensure that your account was not accessed by an
unauthorized third party. Because protecting
NAVY FEDERAL CREDIT UNION ACCOUNT UPDATE
We
recently reviewed your account, and we suspect an unauthorized ATM -
based transactions on your account access. Our banking service will help
you to avoid frequently fraud transactions and to keep your savings and inve
Security Center
Military Grade Encryption is Only the StartAt PayPal, we want to increase your security and comfort level with every transaction. From our Buyer and Seller Protection Policies
Security Center
Military Grade Encryption is Only the StartAt PayPal, we want to increase your security and comfort level with every transaction. From our Buyer and Seller Protection Policies
Dear PayPal Member,
PayPal is committed to maintaining a safe environment for its community of
buyers and sellers. To protect the security of your account, PayPal employs
some of the most advanced security systems in the world and our anti-fraud
teams regularly screen the PayPal system for un
Ref. Number: 132/756/4509
Batch Number: 538901527-Bc68
Ticket Number: 27522465896-6453
Dear Sir/Madam,
We are pleased to inform you of the result of the Winners
in our International Lottery Program held on the 2nd of
January, 2005. Your e-mail address attached to ticket
number 27522465896-6453
Dear SunTrust customer,
We recently reviewed your account, and suspect that your Suntrust Internet Banking account may
have been accessed by an unauthorized third party. Protecting the security
of your account and of the Suntrust network is our primary concern. Therefore,
as a pr
Dear SunTrust customer,
We recently reviewed your account, and suspect that your Suntrust Internet Banking account may
have been accessed by an unauthorized third party. Protecting the security
of your account and of the Suntrust network is our primary concern. Therefore,
as a pr
u that you have
emerged a winner under the First Category, which is
part of our promotional draws. The draws were held on
the day prior to your notification and results are
being officially announced . Participants were
selected through a computer ballot system drawn from
2,500,000names/email ad
FROM: PROMOTIONS DEPARTMENT OF INTERNATIONAL LOTTO BV WINNING NOTICE
FOR CATEGORY A WINNER -
Ref No:lL/03/357856256/NL
Attention:
International Lotto BV has just concluded its final draws of it's periodical
promotional program. An exclusive list of email addresses of thousands of
individual an
8/RDL.
DATE: 13TH April 2004
ATTN: WINNER ,
RE: AWARD NOTIFICATION FINAL NOTICE.
We are pleased to inform you of the release on 16 March, 2004 of the result of the
FLASH FORTUNE LOTTO, Spanish sweepstake lottery Intl promotion. Programs held o
From: Hassan Uday
Without the death of Qusay and Uday (sons of Saddam Hussein) his brother who
abandoned me and my mother i would'nt have come out to say this but i can still thank
Allah for this oppotuinity.
He promised to take care of my mother and i with t
This report relates to a message you sent with the following header fields:
Return-path: <[EMAIL PROTECTED]>
Return-path: <[EMAIL PROTECTED]>
Received: from ims-ms-daemon.imss2.tm.net.my by imss2.tm.net.my
(iPlanet Messaging Server 5.1 HotFix 1.9 (built Dec 3 2002))
id <[EMAIL PROTECT
RE: AWARD WINNING NOTIFICATION.
WE ARE PLEASED TO INFORM YOU ABOUT THE RELEASE TODAY THE 2nd OF SEPTEMBER, 2003 OF
SWEEPSTAKE LOTERIA
PRIMITIVA DE ESPAÑA HELD ON THE AUGUST30TH 2003, YOUR COMPANY NAME ATTACHED TO TICKET
NUMBER: 564- 40996-ES, WITH SERIAL NUMBER 5388
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
[EMAIL PROTECTED]
Reporting-MTA: dns;jisuserver
Received-From-MTA: dns;218.144.121.214
WERKEN BIJ DE LOTTO,
41132, NL-1007 DB AMSTERDAM,
THE NETHERLANDS.
FROM: THE DESK OF THE DIRECTOR PROMOTIONS,
INTERNATIONAL PROMOTIONS/PRIZE AWARD DEPARTMENT,
REF: WBL/67-B773524441
ATTN:
AWARD NOTIFICATION; FINAL NOTICE
We are pleased to inform you of the announcement
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> the way I read the diskfs code, requesting file notifications doesn't
> add a reference to the node. So when you request notifications as a
> user, you have to keep the port around to receive notifications.
> Is this how it is intended to be?
Seems
Hi,
the way I read the diskfs code, requesting file notifications doesn't
add a reference to the node. So when you request notifications as a
user, you have to keep the port around to receive notifications.
Is this how it is intended to be?
Just wanna make sure,
Marcus
___
73 matches
Mail list logo
